Mobile Phone Payment Processing Methods and Systems

ABSTRACT

Embodiments provide systems, methods, processes, computer program code and means for using mobile devices to conduct payment transactions at merchant locations including brick and mortar locations and remote locations as well as for person to person transactions.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is based on, and claims benefit and priority of,U.S. Provisional Patent Application Ser. Nos. 61/322,477 (filed on Apr.9, 2010), and 61/362,567 (filed on Jul. 8, 2010) the contents of each ofwhich are incorporated herein in their entirety for all purposes.

BACKGROUND

Credit cards, debit cards and other payment cards have been in use foryears. The manner in which these payment cards are used is substantiallyunchanged since their introduction—a cardholder presents their paymentcard to a merchant, who uses a magnetic stripe reader to read thecardholder's payment account information, and then the merchanttransmits the payment account information along with transaction detailsto a payment network for authorization, clearing and settlement. Whilethis approach has worked well, there are a number of disadvantagesassociated with it.

For example, not all merchants are able to properly secure the userinformation that is read from a payment card. There have been a numberof highly publicized incidents where cardholder data was stolen frommerchant systems. In other incidents, employees directly skimmed orcopied cardholder data and used it for fraudulent transactions. Ifmerchants are required to continue to read, store and transmit paymentcard information, such thefts will persist. Further, the systems andprocedures required to properly save, store and transmit cardholderinformation is a significant cost to merchants. It would be desirable toprovide systems and methods in which payment card information is notstored, captured, or transmitted by merchants.

As another example disadvantage, current payment cards are typicallyassociated with a single payment account. A cardholder may have a numberof payment cards, but must make a conscious decision regarding which one(or ones, in the case of a split tender transaction) of those paymentcards to use in a given transaction. It would be desirable to providesystems and methods which allow a customer to select one or more paymentaccounts for use in conducting a transaction. Further, it would bedesirable to provide a customer with information about which account(s)should be used in a given transaction (e.g., in order to save ontransaction costs, to earn rewards, to manage balances and spend, etc.).

Another disadvantage of existing payment systems is that current paymentcards are unable to easily be used in conjunction with mobile devicessuch as smart phones. Some payment card associations and issuers haveproposed the use of RFID chips or tags installed on mobile phones as away to allow payment card information to be presented at a point of salelocation. However, such solutions require that point of sale deviceshave RFID readers installed. The installation of such devices isexpensive and time consuming. It would be desirable to provide anability to conduct purchase transactions (both online and at brick andmortar stores) using a mobile device.

These, and other, problems are solved by using systems and methods ofthe present invention. Other advantages and features will becomeapparent upon reading the following disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a payment system configured pursuantto some embodiments.

FIG. 2 is a block diagram depicting further details of a payment systemconfigured pursuant to some embodiments.

FIG. 3 is a flow diagram depicting a customer registration processpursuant to some embodiments.

FIGS. 4A-4C are flow diagrams depicting a transaction process pursuantto some embodiments.

FIG. 5 is a block diagram depicting system components of a systempursuant to some embodiments.

FIG. 6 is a block diagram depicting a transaction flow pursuant to someembodiments.

FIG. 7 is a block diagram depicting components of a mobile devicepursuant to some embodiments.

FIGS. 8A-8E are sample user interfaces associated with embodiments ofthe present invention.

FIG. 9 is a table depicting a portion of a customer database pursuant tosome embodiments.

DESCRIPTION

Embodiments of the present invention relate to systems, methods,processes, computer program code, and means for using mobile devices toconduct payment transactions at merchant locations including brick andmortar locations and remote (e.g., such as Internet or mail order andtelephone) locations, as well as for person to person transactions. Insome embodiments, the mobile device can be used to initiate and conductpayment transactions involving a number of different payment accounts,including, for example, credit, debit, deposit, stored value, checkingand other accounts. In some embodiments, a mobile device configuredusing features of the present invention may be capable of initiatingpayment transactions that are processed over a variety of differentpayment networks (e.g., such as the credit card networks operated byVisa, Inc. or MasterCard International Incorporated, private labelprocessing networks, electronic funds transfer networks, AutomatedClearing House networks, or the like). In some embodiments, mobiledevices configured using features of the present invention are capableof determining or suggesting a most desirable payment account to use ina given transaction (e.g., based on one or more predefineduser-specified rules, account characteristics, merchant information orthe like). In this manner, users are provided with greater paymentoptions and better information about which payment account to use in anygiven transaction.

Pursuant to some embodiments, transaction methods, systems, apparatus,means and computer program code are provided for conducting paymenttransactions which include selecting a mobile payment option at a pointof sale, obtaining, using a mobile device, a checkout token printed orotherwise displayed at the point of sale, selecting, using said mobiledevice, a payment account, viewing, on the mobile device, paymenttransaction details associated with a pending payment transaction, andauthorizing, using the mobile device, the payment transaction. Pursuantto some embodiments, the checkout token is obtained by the mobile deviceby capturing a barcode image, key entering the checkout token, bywireless communication or otherwise receiving the checkout token at amobile device.

Embodiments of the present invention are believed to provide desirableadvantages from a fraud reduction standpoint, as the chance for fraud islow, and PCI compliance is made very easy for the merchant for a varietyof reasons, including: (i) the customer's actual payment credentials arenever provided to a merchant, and (ii) the customer's paymentcredentials can never be accessed for use in a payment transactionunless the access request is coming from one of the authorized devicesthat has been designated by the customer as having access to thecustomer's payment credentials.

A number of terms are used herein for convenience and ease ofexposition. For example, the term “capture” will be used to refer to theact of scanning, reading or other capturing of a “checkout token” (anidentifier used to facilitate transactions pursuant to someembodiments). The term “capturing” (or “captured”) is not intended to belimiting, and is intended to encompass embodiments where a mobile deviceis operated to receive a checkout token (or data associated with acheckout token) via key entry, via image capture, via RFID reading, andusing other scanning, reading, or other techniques described herein.Pursuant to some embodiments, the term “capture” further includes anydecoding or image processing of a checkout token required to retrieve orotherwise obtain information from the checkout token.

As another example, the term “wireless” is used to refer to unwiredremote communication techniques, such as, for example, using radiofrequency or other electromagnetic radiation based communicationtechniques (including RFID, wifi, Bluetooth, zigbee or othertechniques). Those skilled in the art, upon reading this disclosure,will appreciate that the use of these terms is not intended to belimiting, but for the purposes of exposition.

INTRODUCTION Illustrative Examples

Embodiments of the present invention allow customers to make purchasesat merchant locations using their mobile devices. In the following, anumber of processes and transaction flows will be described. To help indescribing those processes and transaction flows, two illustrativeexample users will now be introduced. The examples will be used toillustrate features of some embodiments and to aid in describing certainfeatures of the present invention. The examples are not intended to belimiting and are merely provided for illustration.

A first example user is referred to herein as “Jane”. In the example,Jane has four payment accounts that she uses on a regular basis: (i) ahigh interest rate credit card, (ii) a checking account, (iii) a debitcard linked to her checking account, and (iv) a Starbucks® gift card.Jane only likes to use her credit card when she has to, and always wantsto make sure that she keeps at least $1,000 in her checking account.Jane also prefers, when possible, to reduce the amount of fees she hasto pay for any transaction.

A second example user is referred to herein as “Sam”. In the example,Sam has five payment accounts that he uses regularly: (i) a rewardscredit card, (ii) a private label Sears® credit card, (iii) a checkingaccount, and (iv) an American Express® charge card that Sam uses forwork-related expenses. Sam prefers to earn rewards when possible, whichhe earns with his rewards credit card and his Sears private label card(when shopping at Sears), and to put any business-related expenses onhis American Express charge card.

Both Sam and Jane have mobile phones. Sam has a mobile phone that has aWeb browser, and Jane has an Apple iPhone®. Sam will access and use thepayment system of the present invention using his phone's browser, whileJane will access and use the payment system of the present invention bydownloading and configuring an iPhone® application (or “app”) configuredto facilitate payment transactions pursuant to the present invention.

Using features of the present invention, customers such as Jane and Sammay use their mobile devices to pay for products or services at point ofsale (or “POS”) locations. Merchants need not modify their point of salehardware (although some embodiments involve the merchant displaying acheckout token on a point of sale display terminal) and users may payusing their existing payment accounts. Embodiments allow users to chooseamong a variety of payment accounts to use the most appropriate or mostdesirable payment account for a given transaction. Embodiments alsoallow merchants, payment account issuers, and/or payment networkoperators to establish rules governing which payment instruments aremade available for use on the phone. These illustrative examples will beused in conjunction with some of the following description to aid indescribing features of some embodiments of the invention. In FIG. 1, anoverview of a system according to the present invention will bedescribed. In FIG. 2, a more detailed block diagram of some componentsof a system is provided. In FIG. 3, a customer registration process willbe described, and in FIGS. 4A-C transaction processes will be described.

System Overview

Features of some embodiments of the present invention will now bedescribed by reference to FIG. 1, which is a block diagram of a system100 pursuant to some embodiments. As shown, a payment account holder,buyer, or other user or operator (hereafter, the “customer”) may have oruse a mobile device 102 (such as a mobile telephone or the like). Themobile device 102 has a display screen 136 and a data entry device 138(such as a keypad or touch screen). Pursuant to embodiments of thepresent invention, the customer may use the mobile device 102 to conducta purchase transaction with a merchant 108. The merchant 108 may be aphysical storefront, electronic commerce merchant, or mail order andtelephone (“MOTO”) merchant (or another person or entity).

In a typical example transaction, a customer may purchase products orservices from the merchant 108 by first taking the products or servicesto a point of sale (e.g., such as a physical checkout counter, anelectronic shopping cart, or the like, generally referred to herein asthe “point of sale” or “POS”). The merchant 108 begins the checkouttransaction as normal, by totaling the items to be purchased (e.g., byusing a bar code scanner, key entry of product codes, or the like). Themerchant (acting through a clerk, a display screen, a POS terminalfacing the customer, or the like) then prompts the customer to select apayment option. In prior systems, the merchant might prompt the customerto select “credit”, “debit” or another payment option. Pursuant to thepresent invention, the merchant (acting through a clerk, display screen,a POS terminal facing the customer, or the like) may prompt the customerfor those options as well as a mobile payment option. If the customerselects the mobile payment option, features of the present invention areutilized to process the transaction.

In some embodiments, rather than requiring the customer to select themobile payment option by an action (such as by pushing a button on a POSterminal or communicating the choice to a clerk, etc.), the choice maybe made by the customer's act of scanning, capturing or entering acheckout identifier (as discussed below). For example, in suchembodiments, the action of capturing the checkout identifier used in thepresent invention will cause the transaction to proceed pursuant to thepresent invention.

If the mobile payment option is selected, and once the purchase totalhas been generated, the merchant 108 transmits a merchant paymentauthorization request message to a transaction management system 130(via path 116). The merchant payment authorization request message mayinclude one or more pieces of data or information about the transaction.For example, the message may include one or more of a merchantidentifier, the amount due, and a unique checkout token (“checkouttoken”) which, as will be described further herein, is used to identifythe merchant and the transaction for further processing.

A number of techniques may be used to generate or present the checkouttoken. For example, in some embodiments, one or more checkout tokens maybe predefined or established for use with a given merchant 108 (e.g.,the merchant 108 could have a number of checkout tokens available todisplay or present at the point of sale). In such embodiments, themerchant 108 would choose a checkout token for use with a giventransaction. In some embodiments, such checkout tokens may be generatedor provided using a standardized format. As an illustrative example, amerchant 108 may be issued or provided with a range of checkout tokensor a predefined series or sequencing of numbers. As a specific example,a merchant may be instructed to use a range of numbers (e.g., from“00000” to “99999”) as well as a sequencing or usage pattern (e.g., aspecific checkout token may only be used in conjunction with a singleactive transaction). In such an embodiment, the POS system would pass aselected checkout token to the transaction management system 130. Inother embodiments, however, the checkout tokens are issued or selectedby the transaction management system 130 and are provided to themerchant 108 in response to a merchant authorization request message (aswill be described further below). Those skilled in the art willrecognize that other techniques for issuing, using and selectingcheckout tokens may be used.

Pursuant to some embodiments, the checkout token is dynamicallygenerated for each transaction. In some embodiments, the checkout tokenis a static identifier associated with an individual checkout location(e.g., such as a specific point of sale terminal or location, or with asmall business person such as a plumber or electrician who has nospecific checkout location, or with an individual). The merchant 108causes the checkout token to be displayed or presented to the customer.For example, the checkout token may be displayed on a display deviceassociated with the merchant, or pre-printed on a placard or otherdisplay near the point of sale.

From the customer perspective, the payment process of the presentinvention may begin with the customer performing an authenticationprocess to confirm their identity and authority to conduct transactionsusing the present invention. The authentication process may be performedafter, or in some situations, prior to the customer's selection of themobile payment option at the point of sale. Pursuant to someembodiments, the authentication process serves to authenticate thecustomer to the transaction management system 130. The authenticationprocess may involve the customer launching a mobile payment applicationor a Web browser on the mobile device 102 and providing one or morecredentials or items of information to the transaction management system130 via communication path 114. For example, the authentication processmay involve the entry of a user identifier, a password, or othercredentials into a login screen or other user interface displayed on adisplay device 136 of the mobile device 102. The transaction managementsystem 130 compares the received information with stored information toauthenticate the customer.

The authentication process, in some embodiments, also involves thecomparison of one or more attributes of the mobile device 102 with astored set of attributes collected from the mobile device 102 during aregistration process (such as the process of FIG. 3). For example, theattributes may include identifiers associated with the mobile device 102which uniquely identify the device. In this way, the customer isauthenticated two ways—with something they know (login credentials), andsomething they have (mobile device). Once the customer is successfullyauthenticated, then the system has access to a variety of attributesabout the customer, including a list of payment accounts that thecustomer previously identified to the transaction management system 130as part of the registration process.

After a successful authentication process, the customer is prompted toscan, capture (or otherwise enter) a checkout token from a deviceassociated with the merchant 108 (shown as interaction 112 between themobile device 102 and the merchant 108). The checkout token is used, aswill be described further herein, to link messages from the mobiledevice 102 and the merchant 108, and the transaction management system130, so that transactions pursuant to the present invention may beaccomplished. After capture of the checkout token, the mobile device 102transmits the token to the transaction management system 130 in acustomer transaction lookup request message (over communication path114). The customer transaction lookup request message includes thecheckout token captured by the mobile device 102.

Pursuant to some embodiments, either a “static” checkout token or a“dynamic” checkout token may be used. In an embodiment where a “static”checkout token is used (e.g., such as one that is assigned for use by aspecific checkout location and which does not include any variableinformation for each transaction), the transaction management system 130matches the information in the customer transaction lookup request(received from the mobile device 102) with the information in themerchant payment authorization request (received from the merchant 108)by matching the checkout token information received in each of themessages. Once a match is found, the transaction management system 130transmits a transaction detail message (via path 114) to the customer'smobile device 102. The information from the transaction detail messageprovides the customer with details about the transaction, including butnot limited to the amount due, the name and location of the merchant(information contained in or derived from the merchant paymentauthorization request), and possibly one or more marketing messages. Inaddition, the transaction management system may also send to the phone alist of payment accounts the customer has registered with the system,including credit, debit, checking, prepaid and other types of accounts.The list of accounts may include all of the accounts the customerregistered with the system, or it may include a subset of accounts,based on rules established by the mobile payment network operator, themerchant, the issuer of each payment account, the customer, or anotherentity (e.g., the list of accounts sent to the mobile device may onlyinclude those accounts that may be used for the current transaction).Now the customer can see on the display 136 of their mobile device 102the name of the merchant they are about to pay, the amount to be paid,and a list of their payment accounts they can use to pay the merchant108.

In some embodiments, the merchant's checkout token may be derived from aunique identifier in the merchant payment authorization request. Forexample, in cases where the merchant can't easily modify their system topass the transaction management system 130 a static checkout token, sucha derivation may reduce or even eliminate the need for equipmentupgrades and software changes that might otherwise be required by amerchant adopting a new payment method. The checkout token may bederived using a mapping table which maps a merchant identifier, aterminal identifier, or other information (passed by the merchant systemto the transaction management system 130) to a checkout token. Based onthe received identifier, a mapping process may occur to identify theappropriate checkout token for use in that payment transaction. Theselected checkout token is associated with the transaction in themerchant transaction queue where it is made available to be matched withtransactions from the customer message queue. Those skilled in the artwill recognize that other matching and mapping techniques may also beused. In either event, the checkout token is an identifier (consistingof a combination of letters, numbers, and/or symbols) used to link amerchant payment authorization request to a payment authorizationrequest received from a customer operating a mobile device pursuant tothe present invention.

In embodiments using a “dynamic” checkout token (e.g., where thecheckout token is generated by either the merchant 108 or thetransaction management system 130 before it is displayed on a displaydevice associated with the merchant during a checkout transaction, andwhere the checkout token may include additional information about atransaction), checkout processing may proceed without a need for acustomer transaction lookup request message to be transmitted to thetransaction management system 130. For example, in some embodiments,some or all of the transaction details may be encoded in a dynamiccheckout token which, when captured and processed by the mobile device102, provides the transaction details to the mobile device 102. Furtherdetails of both “static” and “dynamic” checkout token embodiments willbe discussed further below. In either event, however, the checkout tokenis used to match messages from the mobile device 102 with messages fromthe merchant 108 at the transaction management system 130.

To complete the payment transaction, the customer then interacts withthe mobile device 102 to select a desired payment account to use in thepresent transaction, and causes a customer payment authorization requestmessage to be submitted (via path 114) to the transaction managementsystem 130. In some embodiments, the transaction management system 130transmits a payment authorization request message to the customer'smobile device, enabling the customer to have a final opportunity toconfirm or cancel the payment transaction, although this step isoptional. The customer's confirmation or cancellation is transmittedfrom the mobile device 102 as a customer payment authorization messageto the transaction management system 130 via path 114.

Once the payment authorization message from the customer's mobile deviceis received, the transaction management system 130 creates anauthorization approval request message for transmission through one ormore payment processing networks (not shown in FIG. 1) to cause theauthorization, clearing and settlement of funds for the transaction.This request message includes information from the merchant paymentauthorization request such as the amount of the transaction, or at leasta pointer or reference to the relevant merchant payment authorizationrequest (received from the merchant 108) and a payment accountidentifier identifying the payment account selected by the customer andpreviously stored in the transaction management system 130. Theauthorization approval processing is performed using standard financialauthorization processing over one or more authorization networks (e.g.,such as the VISANET® network operated by Visa, Inc., an AutomatedClearing House system such as NACHA, or the like). Once the availabilityof funds is confirmed, the transaction management system then sends themerchant payment authorization response message (via path 116) to themerchant so the transaction can be completed at the point of sale. Acustomer payment authorization response message may also be displayed tothe customer at the point of sale and/or transmitted to the customer'smobile device.

Pursuant to some embodiments, as will be described further below, themerchant 108 is not provided with any actual payment credentials of thecustomer during the checkout process. Further, the mobile device 102never stores, sends or receives actual payment credentials. Instead, themobile device 102 stores or has access to a proxy associated with actualpayment credentials, and the proxy is used to identify a desired paymentaccount for use in a given transaction. The proxy is transmitted to thetransaction management system 130 in a customer payment authorizationrequest message and the transaction management system 130 uses the proxyto lookup or identify the actual payment credentials associated with theselected account. The actual payment credentials are then transmittedfrom the transaction management system 130 to an account issuer or agentfor authorization. By ensuring that actual payment credentials are notrevealed to or stored at a merchant 108 or mobile device 102,embodiments provide increased account security and reduced potential forfraud or abuse.

Pursuant to some embodiments, the mobile device 102 may be a smart phoneor a Web enabled mobile device such as, for example, an iPhone®, anAndroid® phone, or any phone that can access and display Web content oraccess the Internet. In some embodiments, the mobile device 102communicates with transaction management system 130 using a cellular orwireless network. In some embodiments, the transaction management system130 is a secure server (or network of servers). In some embodiments, thetransaction management system 130 is in communication with one or morepayment processing networks (not shown in FIG. 1) such as the VISANET®network operated by Visa Inc., the BANKNET® network operated byMasterCard International, or the like. The transaction management system130 may also be in communication with other financial transactionnetworks (such as ACH and EFT networks, private label networks,alternative payment systems such as PayPal®, or the like) to allowcustomers operating mobile devices 102 to conduct transactions using awide variety of different forms of payment instruments and accounts. Thetransaction management system 130 may further be in communication withone or more ad or offer management networks, such as those provided byGoogle®, Apple®, Yahoo®, Microsoft® or the like. As will be describedfurther below, data, including advertisements and offers may be receivedfrom those networks and presented to customers via the mobile device102.

Although the system depicted in FIG. 1 (and elsewhere throughout thisdisclosure) shows only a single mobile device 102, merchant 108 andtransaction management system 130, those skilled in the art willappreciate that in use there will be a number of devices in use, anumber of merchants using the system, and potentially multiple instancesof the transaction management system in operation.

As will be described further below, transactions conducted usingembodiments of the present invention have a number of desirableadvantages over existing payment methods. For example, customers areable to conduct payment transactions at a wide variety of merchantlocations using their mobile device. Further, the mobile device may beused to access a variety of different payment accounts held by thecustomer, allowing the customer to select the most appropriate ordesirable payment account for each transaction. Using features of thepresent invention, merchants need not undertake costly hardware retrofitor replacements, as embodiments may utilize existing point of salesystems and hardware. In addition, paying with embodiments of thepresent invention can be more secure than existing payment methods, asit is possible to require that each transaction be authenticated usingtwo items—user information (such as a user identifier and/or password,or a PIN) known to the customer, as well as unique attributes associatedwith the mobile device the customer uses to initiate the transaction.Other benefits and advantages will become apparent to those skilled inthe art upon reading this disclosure.

Further System Details

Further details of some aspects of a system according to someembodiments of the present invention will now be described by referenceto FIG. 2. FIG. 2 is a block diagram of an example payment systemnetwork environment showing communication paths between a mobile device202, merchants 208, transaction management system 230 and paymentprocessing systems 232. Mobile device 202 may be, for example, a mobiletelephone, PDA, personal computer, or the like. For example, mobiledevice 202 may be an iPhone® from Apple, Inc., a BlackBerry® from RIM, amobile phone using the Google Android® operating system, or the like.Pursuant to some embodiments, mobile device 202 may operate a paymentapplication allowing mobile device 202 to operate as a payment device asdescribed herein. In some embodiments, mobile device 202 is capable ofaccessing and displaying Web content or otherwise accessing the Internetso that a customer operating mobile device 202 may interact withtransaction management system 230 to initiate a transaction via a Webinterface.

Mobile device 202 of FIG. 2 can, for example, communicate over one ormore wired and/or wireless networks 201. As an example, a wirelessnetwork can be a cellular network (represented by a cell transmitter215). A mobile device 202 may communicate over a cellular or otherwireless network and through a gateway 216 and then communicate with anetwork 214 (e.g., such as the Internet or other public or privatenetwork). An access point, such as access point 218 may be provided tofacilitate data and other communication access to network 214. Accesspoint 218 may be, for example, compliant with the 802.11g (or other)communication standards. For example, in embodiments in which a mobiledevice 202 is operating a payment application which allows mobile device202 to function as a payment device pursuant to the invention, thepayment application may cause or control communication of data throughnetwork 201 to transaction management system 230.

In some embodiments, mobile device 202 may engage in both voice and datacommunications over wireless network 214 via access point 218. Forexample, mobile device 202 may be able to place or receive phone calls,send and receive emails, send and receive short message service (“SMS”)messages, send and receive email messages, access electronic documents,send and receive streaming media, or the like, over the wireless networkthrough access point 218. Similar communications may be made via network215.

In some embodiments, a mobile device 202 may also establishcommunication by other means, such as, for example, wired connectionswith networks, peer-to-peer communication with other devices (e.g.,using Bluetooth networking or the like), etc. Mobile device 202 can, forexample, communicate with one or more services over networks 201, suchas the transaction management system 230 (to conduct paymenttransactions, to create, edit, view or otherwise modify payment accountsettings and preferences, etc.), the Web 240, and other services 242.Mobile device 202 can also access other data over the one or more wiredand/or wireless networks 201. For example, content providers, such asnews sites, RSS feeds, web sites, blogs, social networking sites,developer networks, etc., can be accessed by mobile device 202. Suchaccess can be provided by invocation of a web browsing function orapplication (e.g., a browser) in response to a customer launching a Webbrowser application installed on mobile device 202. In some embodiments,a user may utilize a Web browser to interact with transaction managementsystem 230 to register payment accounts, establish account preferences,perform payment transactions, etc.

Mobile device 202 has a display screen 236 and a data entry device 238(such as a keypad or touch screen, or voice interface). Pursuant toembodiments of the present invention, the customer may use the mobiledevice 202 to conduct a purchase transaction with a merchant 208.Merchant 208 may be a physical storefront, electronic commerce merchant,or MOTO merchant (or another person or entity). Mobile device 202, insome embodiments, also has a camera (not shown) or other image capturedevice which allows the mobile device 202 to capture an image orrepresentation of a checkout token 210. Mobile device 202, in someembodiments, also has a wireless receiver (not shown) or other wirelesssignal receiving device which allows the mobile device 202 to capture awireless signal representation of a checkout token 210. For example, acustomer may operate mobile device 202 to take a digital picture orcapture the image of a checkout token 210 displayed on or at a merchantpoint of sale device to initiate a payment transaction using the presentinvention. The captured image is shown as item 237 on the display screen236. As will be described further below, the checkout token 210 may beused to initiate and conduct transactions with a merchant.

Merchant 208 may operate one or more merchant systems 209 to processpayments and transactions, including, as will be described, paymenttransactions pursuant to the present invention (as well as “traditional”or standard payment transactions involving cash, standard payment cards,or the like). Merchant system 209 may be a networked point of salesystem (such as for a physical retail location) or it may be a shoppingcart system (such as for an electronic commerce or Internet retaillocation). Merchant system 209 may further be a combination of systemsdesigned to allow a merchant to accept payments for goods or services.In some embodiments, merchant system 209 may be in communication withone or more point of sale devices 212 which have display devices 213 forpresenting and receiving information from customers. For example, in thesituation where the merchant 208 is a physical retail location, amerchant system 209 may be in communication with a number of differentpoint of sale devices 212 each of which is located at a differentcheckout lane or location within the store (or in different stores indifferent geographical locations). Each of the point of sale devices 212may present, display, or communicate transaction information tocustomers at the point of sale (or “POS”) so that the customer canapprove or authorize purchases and present payment for the purchases.

As another example, where the merchant 208 is an Internet or otherelectronic commerce merchant, the merchant system 209 may be a Webserver (or a network of servers, some of which may be Internetaccessible) configured to process purchase transactions associated withmerchant 208. Point of sale devices 212, in such an example, may be anumber of remote terminals interacting with merchant system 209 such as,for example, personal computers, mobile devices, or the like that areable to interact with the merchant system 209 via a network such as theInternet. Because embodiments of the present invention are capable ofinitiating and conducting transactions for both physical and remotetypes of merchants, the point of sale, point of purchase, or interactionbetween a buyer and merchant may be referred to as the “point of sale”herein.

Pursuant to embodiments of the present invention, a checkout token 210is displayed on or near the point of sale. The checkout token 210 may beeither a “static” checkout token or a “dynamic” checkout token. Insituations where static checkout tokens are used, the token may beprinted, displayed, or provided near the point of sale location (such ason a sticker or placard displayed so the customer can easily see andread or capture the token). Static checkout tokens 210 may be printed asa bar code image, as an alphanumeric identifier, or in other forms. Ingeneral, checkout tokens may be presented in forms which are easilydiscernable by a human so that they may be both key-entered or capturedusing a mobile device 202. In embodiments where static checkout tokensare used, an additional processing step may be performed (as will bedescribed further below) in order to provide the mobile device 202 withdetailed information about the transaction.

In embodiments where dynamic checkout tokens are used, the token may bedisplayed on a display device 213 associated with a point of sale device212. A dynamic checkout token may be generated to include transactioninformation (e.g., such as the purchase amount, etc.) and may, in someembodiments, involve fewer messages between the mobile device 202 andthe transaction management system 230 during a payment transaction. Thecheckout token 210 may be encoded or displayed as a bar code image, asan alphanumeric identifier, as a wireless signal, or in other forms toallow the checkout token 210 to be captured as an image (e.g., using acamera or scanner associated with the mobile device 202). The checkouttoken 210 may also be key entered by a customer of the mobile device 202or be captured by a wireless receiver associated with the mobile device202. In some embodiments, a mobile device may be operated in conjunctionwith multiple types of checkout tokens 210 (e.g., a mobile applicationmay be capable of capturing a checkout token 210 using image capture,wireless receiving, or key entry, depending on how the checkout token210 is presented at a point of sale).

The display device 213 could be an LCD (or other display technologies)display (e.g., such as those currently available at many merchants insystems such as the Hypercom 4150 terminal, or the Verifone MX870terminal or the like). The use of the checkout token 210 in transactionspursuant to the present invention will be described further below. Ingeneral, however, the checkout token 210 is used by the transactionmanagement system 230 to match a payment request from a mobile device202 with a payment authorization request from the merchant 208 tocomplete a payment transaction using information stored at, oraccessible to, the transaction management system 230. In embodimentswhere the checkout token 210 is a dynamic checkout token, the token mayfurther be used to communicate transaction details from the merchant 208to the mobile device 202.

In a typical example transaction, a customer may purchase products orservices from the merchant 208 by first selecting mobile payment as apayment option, performing an authentication process with a paymentapplication on a mobile device 202 (or via a Web browser interactingwith transaction management system 230), capturing a checkout token 210from a device associated with the merchant 208 (such as from a display213 of a point of sale device 212), receiving transaction details and apayment account list or list of preferred or eligible accounts from thetransaction management system 230, selecting a payment option on themobile device 202, and submitting a customer payment authorizationrequest to a transaction management system 230 over a network 201.

The selection of a payment option involves receiving informationidentifying one or more payment accounts available to the customer. Theavailable payment accounts may be those specified by the customer duringa registration process such as the process described further below inconjunction with FIG. 3. Pursuant to some embodiments, the presentationof the different payment account options may include applying one ormore rules or preferences to a list of available payment accounts sothat the customer is presented with the account(s) that are best suitedor available for the current transaction. The customer selects thepayment account (or accounts, in the case of a split tender transaction)to use and the information is transmitted to the transaction managementsystem 230. In some embodiments, all of the customer's available paymentaccounts may be displayed to the customer after the customer has beenauthenticated.

In some embodiments, the list of accounts later received from thetransaction management system (after it processes the customertransaction lookup request) may include additional metadata orinformation associated with each payment account (e.g., such as thecurrent available account balance, any special offers available if theaccount is used in the current transaction, etc.). In some embodiments,the list of accounts later received from the transaction managementsystem may include fewer accounts based on the application of rules atthe transaction management system (e.g., such as the application of oneor more customer, merchant or system rules). For example, a rule mayspecify that a specific payment account not be used for low dollar valuetransactions. In such a case, that specific payment account would not beincluded in the list of accounts sent from the transaction managementsystem in response to the customer transaction lookup request. Putanother way, the list of payment accounts received from the transactionmanagement system after it processes the customer transaction lookuprequest may be a subset of all the accounts the customer has registered.

Substantially at the same time, the merchant 208 transmits a merchantpayment authorization request message to the transaction managementsystem 230 over a network 220. The transaction management system 230matches the customer payment authorization request (received from themobile device 202 over network 201) with the merchant paymentauthorization request (received from the merchant 208 over network 220)by using the checkout token 210.

In some embodiments where a dynamic checkout token 210 is used, notransaction details need be received by the mobile device 202 from thetransaction management system 230—instead, the transaction details maybe provided to the mobile device 202 via data encoded or otherwisecontained in the dynamic checkout token 210. In some embodiments, themobile device 202 requests or receives some or all of the transactiondetails from the transaction management system even where a dynamiccheckout token is used.

In some embodiments, the transaction management system 230 thentransmits a customer payment confirmation request message to thecustomer's mobile device 202, enabling the customer to have a finalopportunity to confirm or cancel the payment transaction. For example,the customer may be prompted to “confirm” or “cancel” the paymenttransaction. The prompt may provide additional information about thetransaction and the selected payment account so the customer can havedetailed information about the transaction before selecting “confirm” or“cancel”. In some embodiments, customers may be given the opportunity toset preferences or otherwise configure the mobile payment application toenable or disable certain messages or transaction steps. As a specificexample, customers may be given the opportunity to receive (or notreceive) customer payment confirmation request messages.

Once the final confirmation to proceed with the payment has beenreceived from the customer's mobile device 202, the transactionmanagement system 230 creates an authorization approval request messagefor transmission through one or more payment processing network(s) 232to cause the authorization, clearing and settlement of funds for thetransaction. This request message includes the transaction details, suchas the amount of the transaction or other information, from the merchantpayment authorization request (received from the merchant 208) and theactual payment credentials associated with the payment account selectedby the customer. The actual payment credentials may be obtained by usingthe payment account selection information and performing a lookup ofactual payment account credentials previously stored in a database orlocation accessible to the transaction management system 230. Theauthorization approval processing may be performed using standardfinancial authorization processing over one or more payment processingnetworks 232 (e.g., such as the VISANET® network operated by Visa, Inc.,an Automated Clearing House system such as NACHA, or the like). Once theavailability of funds is confirmed, the transaction management systemthen sends a merchant payment authorization response message to themerchant 208 so the transaction can be completed at the point of sale212, and a customer payment authorization response message to thecustomer's mobile device 202.

Customer Registration Process

Pursuant to some embodiments, before a customer can use a mobile device(such as the mobile device 202 of FIG. 2) to conduct a purchasetransaction using the present invention, the customer must perform aregistration process such as the process described in conjunction withFIG. 3. Data collected or provided in association with the process 300may be stored at or be accessible to one or more databases associatedwith the transaction management system 230. An example database is shownin FIG. 9 (which will be referenced in conjunction with the followingdescription of process 300).

The registration process 300 of FIG. 3 begins when a customer first (at302) interacts with a registration server (which may be a component of,or related to, transaction management system 230 of FIG. 2) to initiatea registration process. For example, the customer may operate anInternet browser (either on a mobile device or another computing device)to access a registration Web page associated with the registrationserver. The registration Web page may request the customer provide someidentifying information to begin the account creation process. Forexample, a customer may provide name, address and other contactinformation as well as contact preferences, including one or more emailaddresses and phone numbers. A customer identifier or other uniquerecord (or records) may be established in a database as illustrated intable of FIG. 9. A customer identifier U1002 may be used to uniquelyidentify the customer. The customer identifier U1002 may be analphanumeric identifier assigned by the transaction management system230 or may be information based on or provided by the customer (e.g.,such as a mobile phone number or identifier associated with a mobiledevice 202).

Processing continues at 304 where the customer establishes an account.In some embodiments, the account creation includes providing contact andidentifying information associated with the customer, as well asinformation identifying one or more mobile device(s) from which thecustomer wishes to make transactions. Each mobile device 202 may, forexample, be identified by its phone number and/or other uniqueidentifier(s) (such as a hardware serial number, an ASIN, a UUID in thecase of an iPhone, a component serial number such as a CPU serial numberor the like). In some embodiments, where the customer registers from abrowser on their mobile device, or by first downloading a paymentapplication having a registration module onto their mobile device, thesystem may capture unique identifying information associated with themobile device (e.g., such as a hardware serial number, an ASIN, a UUIDor other device identifiers).

Processing continues at 306 where the customer provides informationabout one or more payment devices or payment accounts that the customerwishes to have associated with the payment system of the presentinvention. For example, the customer may enter information about one ormore credit cards, debit cards, gift cards, bank accounts, checkingaccounts, or the like. The information about each account includes theactual payment credentials or sufficient information to process atransaction using the account. For example, with respect to a credit ordebit card, the information may include: the primary account number (orPAN), the expiry date, and the verification code. With respect to a bankaccount, the information may include: the routing number and the accountnumber. Other information, such as bank or issuer information may alsobe entered at 306. Some or all of the information may be stored in oneor more fields of the database table shown in FIG. 9. As shown in FIG.9, a customer may register several payment accounts, and the details areshown as being stored in a field 1010 labeled “Account(s)”.

Referring to the illustrative examples introduced above, the customernamed “Jane” has entered details about four of her payment accounts thatshe would like to be able to utilize in conjunction with the presentinvention, including: a Chase Credit Card, having a primary accountnumber (or “PAN”) of #######, and a card expiration date of 05/12, aWebster Bank Checking account having an ABA number of ####### and anaccount number of ########, a Webster Bank Visa debit card having a PANof ######## and a card expiration date of 06/11, and a Starbucks giftcard having a PAN of ###### and an expiration date of 8/10. Additionalaccount identifying information may be provided as required (e.g., insome embodiments, for payment cards, a card verification number may alsobe provided). The data provided in the table of FIG. 9 is securelystored in a PCI compliant database. In some embodiments, by securelystoring payment card data (including expiry date and verificationcodes), payments made using the present invention may qualify forreduced interchange as “card present” transactions. Pursuant to someembodiments, a customer may add, remove or update account information asneeded.

Processing continues at 308 where the customer may optionally establishone or more preferences or rules associated with the use of one or moreof the accounts entered at 306. For example, the customer may designateone of the accounts as the “primary” or default account. Other rules andpreferences may also be set to enable accounts to be selected and usedin an efficient and logical manner. For example, a customer may specifypriorities or other account-based rules to indicate how a particularpayment account should be treated with respect to other paymentaccounts. A customer may also specify spend limitations or balancerequirements that govern how and when a payment account is to bepresented as an option. A customer may also specify the order in whichaccounts are displayed on the mobile phone, based on what merchant theyare purchasing from, or the funds available in each account, or therewards received for using each account.

In some embodiments, a rule (such as a customer-specified rule), maycause a payment process to proceed more quickly, or with fewer customersteps. For example, a customer may specify that when making a purchase(or a certain type of purchase, such as a purchase below a certaindollar amount) at a specific merchant, that a default payment account beused. In such situations, a purchase transaction using the presentinvention may proceed without need for the customer to select or confirmthe selection of a payment account—it is done automatically byapplication of the customer-specified rule.

Those skilled in the art will appreciate, upon reading this disclosure,that a wide variety and type of account-level rules may be specified toallow a customer to manage how (and when) payment accounts are presentedas payment options.

In the illustrative embodiment introduced above (and in the table ofFIG. 9), the customer named “Jane” has specified the following accountpreferences: (i) she wants to reduce the use of credit, and (ii) shewants to reduce transaction fees. Jane has also specified rules to beapplied when specific payment accounts are analyzed for use in a giventransaction: (i) her Starbucks gift card balance should be used wherepossible (having been assigned the highest priority), (ii) her checkingaccount or the debit card associated with her checking account should beused as the second highest priority (although she prefers not to use thechecking account if a transaction would reduce her balance to below$1,000), and (iii) her credit card should be the final payment option,having the lowest priority.

When Jane uses her mobile device to conduct a transaction using thepresent invention, the transaction management system will compare therules and preferences Jane has specified to the details of thetransaction to recommend which payment account(s) are available for thetransaction. For example, if Jane uses her mobile device to purchase acup of coffee at Starbucks, the transaction management system will lether know that she can use her Starbucks gift card for the purchase. Inthis manner, customers having a variety of payment accounts may bepresented with choices of payment options that are based on theiroverall preferences and usage objectives. Further, a payment accountthat is unavailable or unsuitable for a particular transaction may beidentified as such by the transaction management system so that thecustomer need not be presented with that payment account as an option(e.g., if Jane is purchasing gas at a gas station, she will not bepresented with the Starbucks gift card as a payment option for thattransaction). Further details of how payment accounts are presented to acustomer during a transaction are provided below in conjunction withFIG. 4B and FIG. 8.

In some embodiments, processing may continue at 310 if the customeroperates or uses mobile devices that are capable of operating anapplication that is associated with the present invention (such as aniPhone or an Android phone). At 310, the customer is prompted todownload and install an application on their mobile device. Theapplication allows the customer to operate their mobile device toquickly and easily conduct payment transactions pursuant to the presentinvention. For phones or devices that are not capable of running such anapplication, a link or Web page may be created or provided to thecustomer that may be accessed via a mobile phone browser, so that thecustomer can conduct payment transactions pursuant to the presentinvention.

Once a customer has established an account and registered one or morepayment accounts with the transaction management system, the customermay utilize the system of the present invention to conduct purchasetransactions at merchants that support transactions of the presentinvention.

Transaction Process

An illustrative transaction process 400 will now be described inconjunction with FIGS. 4A-C (while also referring to the components ofsystem 200 of FIG. 2). FIG. 4A depicts a transaction process from theperspective of a merchant (such as merchant 208), FIG. 4B depicts atransaction process from the perspective of a mobile device (such asmobile device 202), and FIG. 4C depicts a transaction process from theperspective of transaction management system (such as system 230 of FIG.2). In general, the three transaction processes are performed inparallel or in conjunction with each other to perform a paymenttransaction pursuant to some embodiments of the present invention. Eachof the transaction processes of FIG. 4 begin when a customer (whoparticipates in the payment system of the present invention) is doneshopping or is otherwise ready to make a purchase at a point of sale.For example, the processes may begin once a customer has selected goodsor services to purchase and has taken them to a point of sale topurchase them. The point of sale may be a checkout lane at a retailstore, an electronic shopping cart at an ecommerce store, a clerk orwaiter at a restaurant, a gas station pump, or the like, or it may beone person using the present invention to pay another person.

Reference is first made to FIG. 4A, where a transaction process 400 isshown. The process of FIG. 4A is generally presented from theperspective of a merchant. For example, transaction process 400 may beperformed by or at a merchant 208 and may be performed using software orsystems associated with a merchant 208 such as, for example, merchantsystem 209 and point of sale device 212. Processing begins at 402 wherethe goods or services are rung up to total the purchase. Processingcontinues at 404 where the point of sale device 212 (or the clerk)prompts the customer to select a payment option, and a determination ismade whether a mobile payment option is selected. If the mobile paymentoption is not selected, processing continues at 406 where standardpayment processing or processing to complete the purchase using anotherpayment option occurs.

If the mobile payment option is selected, processing continues at 408where the merchant system 209 create and transmit a merchant paymentauthorization request, including a merchant checkout token (inembodiments where a checkout token is sent from the merchant), atransaction amount, and other transaction data (such as a terminalidentifier, date, time, enhanced transaction data, etc.) to atransaction management system 230 (e.g., via a network such as network220). The merchant payment authorization request is then used by thetransaction management system 230 (as will be described further below inconjunction with FIG. 4C), to create a pending transaction in a merchanttransaction queue. In some embodiments, as discussed above, the checkouttoken is not sent from the merchant system 209. Instead, the checkouttoken may be retrieved, generated or “looked up” by the transactionmanagement system 230 in response to a message received at 408 frommerchant system 209. For example, the checkout token may be looked upfrom a table associating a merchant ID (received at 408) with a staticcheckout token. In some embodiments, the checkout token could begenerated by the transaction management system 230 when it receives themerchant payment authorization request at 408, and then the checkouttoken would be passed back to the merchant system 209 as part of theacknowledgement of the merchant payment authorization request. Althoughprocessing at 408 is shown as including a checkout token transmittedfrom the merchant to the transaction management system 230, in someembodiments, the token is not sent at 408, instead, the checkout tokenis provided by the transaction management system 230.

Processing continues at 410 where a checkout token is displayed orotherwise provided to the customer. Processing at 410 may be performedin a number of different ways, depending, in some embodiments, onwhether a static checkout token or a dynamic checkout token is used. Insituations where static checkout tokens are used, the display of thecheckout token may be performed prior to the transaction by placing orotherwise displaying a static checkout token in an area associated withthe point of sale device 212. In some embodiments, for example, staticcheckout tokens may be used in applications where a merchant would notwant to incur the cost of purchasing and deploying a display device atthe point of sale for displaying dynamic checkout tokens, and where onlyone checkout event occurs at a time at each checkout location. Forexample, a sticker or placard may be created with the static checkouttoken on it and displayed near the point of sale device 212 so customersand clerks can easily see the static checkout token. The static checkouttoken may be used for multiple transactions and may remain static for arelatively long period of time (such as days, weeks, months, or evenlonger). The static checkout token is generated such that it uniquelyidentifies details about the merchant, including but not limited to thelocation of the store, the merchant's account number, and the specificpoint of sale device 212 within a store with which the static checkouttoken is associated, and may be an alphanumeric identifier (e.g., suchas a 4-7 character identifier) allowing it to be easily keyed in orentered into a mobile device 202, or it may be an encoded bar codeimage, or a radio signal such as that produced by an RFID device.

In embodiments where dynamic checkout tokens are used, processing at 410may include the generation and then the display of the dynamic checkouttoken. For example, the dynamic checkout token may be created as anencoded bar code image that, when decoded, reveals an identifier thatuniquely identifies a number of items associated with the point of saledevice 212 and a particular checkout transaction. The decoding of thebar code image may, in some embodiments, reveal a checkout identifierthat may be used (e.g., by the transaction management system 230) toidentify information about the POS device 212 such as, for example, themerchant, the particular POS device 212, the lane or checkout location,the location of the merchant, or a particular transaction, etc. Forexample, each dynamic checkout token may be associated with: aparticular merchant, a specific checkout lane at a specific merchantlocation, a particular checkout transaction, and a specific POS device.Each POS device 212 may have a POS identifier, and that POS identifiermay be associated with a specific dynamic checkout token generated for atransaction. As a specific illustrative example, a dynamic checkouttoken generated for a grocery store may identify the name of the grocerystore (e.g., such as the chain), the location of the grocery store (suchas the specific geographical location of the store), the checkout lanewithin the specific store, and the POS device in the checkout lane. Insome embodiments, for each dynamic token there may be several ways theinformation encoded in the token can be used by the transactionmanagement system 230 to reveal information about the merchant or theactual transaction. First, the information can be stored inside thecheckout token itself (in such scenarios, the token may not beappropriate for key-entry by a human, and instead should be captured orscanned by the mobile device). Next, the checkout token itself may be anidentifier that can be used to “lookup” or reference the transactiondetails stored in a database table. In such a case, the checkout tokenmay be, for example, a 4 to 7 position combination of alphanumericcharacters or shapes. Such tokens may be either key-entered by a humanor captured by a mobile device.

In some embodiments, the dynamic checkout token can further be generatedto reveal the total transaction amount and other transaction detailsassociated with the transaction for which the dynamic checkout token wasgenerated. In some currently preferred embodiments, however, the dynamiccheckout token does not include the total transaction amount or othertransaction details—instead, the additional payment related data istransmitted from the merchant to the transaction management system forlater matching and transmission to the mobile device. The moreinformation that is included in a checkout token, the more complex itbecomes for the mobile device to decode the information when it isencoded as a barcode image, or radio signal, which can impact the speedof the checkout process. In addition, keeping checkout tokens short(e.g. 4 to 7 characters, number, or symbols) makes it possible forcustomers to use the present invention with any phone that has abrowser, greatly expanding the number of phones (no image scanner orwireless receiver would be required to be present in the phone) andtherefore the number of consumers who could utilize the presentinvention. Once authenticated, the customer can key in the checkouttoken presented by a merchant to make a payment transaction. For thisreason, it is frequently desirable to have transaction detailinformation be delivered to the mobile device through a network 201rather than through the checkout token 210. In some embodiments, dynamiccheckout tokens (as well as static checkout tokens) may be displayed ona display device 213 associated with a point of sale device 212.

In either embodiment, the checkout token 210 is displayed for scanning,capture or other entry by a customer using their mobile device 202 (aswill be described further below in conjunction with FIG. 4B).

Processing at the merchant 208 continues at 412 where the merchantsystem 209 receives a merchant payment authorization response messagefrom the transaction management system 230. The merchant paymentauthorization response message is generated by the transactionmanagement system 230 after certain customer-related processing steps(described in FIG. 4B) and certain transaction management system-relatedprocessing steps (described in FIG. 4C) have been completed, and after apayment account selected by the customer (using their mobile device 202)has been authorized for the purchase transaction. Processing continuesat 414 where the merchant system 209 is operated to cause the generationof a transaction receipt to complete the transaction.

Of note in the merchant processing described above is that at no point,in some embodiments, does the customer provide actual payment accountdata to the merchant 208. Those skilled in the art, upon reading thisdisclosure, will appreciate that such a process has desirable fraud andother benefits.

Pursuant to some embodiments, the process of FIG. 4A (and similarly, forFIGS. 4B and 4C) may be modified to allow the merchant to transmit amerchant payment authorization request before the transaction total hasbeen calculated. Further, in such embodiments, the customer may capturethe checkout token before the transaction total has been calculated.Such an embodiment generally proceeds as follows. First, at thebeginning of every new checkout event, the merchant transmits a merchantpayment authorization request to the transaction management system 230.This merchant payment authorization request contains informationidentifying the merchant and, in some embodiments, a point of saleterminal identifier and/or a unique transaction identifier, but itcontains no amount due information, as the clerk has either not yetstarted to ring up the goods, or is in the middle of ringing up thegoods. In response to this merchant payment authorization request, thetransaction management system 230 generates a checkout token, and themerchant displays the checkout token to the customer (e.g., on a displaydevice of the point of sale terminal).

Such an embodiment may be provided in situations where the merchantwants the customer portion of the checkout process to go as quickly aspossible. By having the checkout token displayed at the start of thecheckout process, the customer can capture at the beginning or middle(while items are still being scanned and totaled), and doesn't have towait until the final transaction total is calculated. Capturing earlyallows the transaction management system 230 to retrieve the customer'savailable payment accounts that are appropriate for the merchant andcustomer based on any available rules.

Further, in some embodiments, by transmitting the merchant paymentauthorization request early in a transaction (before calculation of atransaction total), the transaction management system 230 has anopportunity to provide any relevant offers, coupons or loyaltyincentives to the customer. For example, if the customer has registeredher loyalty credentials with a particular merchant (such as the exampleintroduced above, where Jane shops at Starbucks frequently), then beforethe total amount due is displayed, the merchant may want to cause anoffer or promotion on the customer's mobile device that are appropriatefor or tailored to the specific customer. This allows for advertisingand promotional offers to be displayed to the customer before theyfinish the checkout process.

In general, a transaction process in which the merchant paymentauthorization request message is generated prior to the calculation of atotal amount due proceeds as follows. First, the merchant paymentauthorization request message is generated and transmitted to thetransaction management system 230. The request does not include thetotal amount due (but includes information identifying the merchantand/or the point of sale terminal or checkout lane). The transactionmanagement system 230 creates a pending transaction record and transmitsa checkout token to the merchant. The merchant then causes the checkouttoken to be displayed or presented to the customer. For example, it maybe displayed to the customer on a display screen of a point of saleterminal while she is waiting for the transaction to be totaled. Thecustomer then captures the checkout token using her mobile device 202.

The mobile device 202 transmits the information (after the customerauthentication process, for example) to the transaction managementsystem 230 and the transaction management system 230 matches theinformation with the pending transaction message. The system 230 returnsinformation to the mobile device 202 including information identifyingthe merchant and possibly a list of available payment accounts (but noamount due as it has not yet been communicated to the system 230). Anytargeted offers or advertisements may also be delivered to the mobiledevice at this time. While the customer is waiting for the transactiontotal, a message may be displayed on the mobile device 202 informing herthat the device is “waiting for an amount due” (or similar message).After the merchant calculates the transaction total, the merchanttransmits the total in an updated merchant payment authorization requestmessage to the transaction management system 230. The system 230 usesthis information to update the pending transaction record and thencauses a message to be transmitted to the mobile device 202 to updatethe mobile device 202 with the total amount due (and may also includeinformation about a list of available payment accounts that may be usedin the transaction). The mobile device 202 may be updated to display thetotal as well as any loyalty savings (if any were earned in thetransaction) as well as the list of available payment accounts. Thecustomer then selects her desired payment account(s) to complete thetransaction as normal. Those skilled in the art will appreciate thatother modifications may be made to some or all of the processes shownherein to achieve different transaction flows.

Reference is now made to FIG. 4B, where a further transaction process420 is shown. The process 420 is shown from the perspective of acustomer operating a mobile device. For example, transaction process 420includes a number of steps that may be performed by a customer operatinga mobile device (such as the device 202 of FIG. 2) to completetransactions pursuant to the present invention. As described above, theprocess 420 may be performed in conjunction with the process 400performed by the merchant 208. Processing begins at 422 where a customerwho is a participant in the mobile payment program of the presentinvention launches a mobile payment application on their mobile device202. The mobile payment application may be an “app” or computer programcode stored on the mobile device 202, or, in some embodiments, themobile payment application may be accessed by pointing a Web browserassociated with the mobile device 202 to a Web page associated with amobile payment application over the Internet. For the remainder of thisdiscussion of process 420, it will be assumed that the mobile paymentapplication is an application stored on the mobile device 202 (but suchdiscussion is not intended to limit the application of the presentinvention to such an embodiment).

Processing continues at 424 where the customer is prompted to enterauthentication information. For example, the customer may be prompted toenter information such as a user identifier, a password, or othercredentials into a login screen displayed on the mobile device 202.Processing at 424 may also include collecting or generatingdevice-related information for use in authenticating the customer. Thecustomer authentication information, as well as any device-relatedinformation, are transmitted to the transaction management system 230(e.g., over a network 201) for authentication by the transactionmanagement system 230 (as described further below in conjunction withFIG. 4C). A determination is made at 426 whether the authenticationpassed or failed (e.g., based on a response received from thetransaction management system 230). If the authentication failed,processing may continue at 428 where the customer is informed of thefailure and is either prompted to use a different form of payment or toreattempt the authentication process.

Processing continues at 430 if the authentication processing issuccessful (that is, if the customer and the device have successfullybeen identified by the transaction management system 230), where themobile payment application enables the customer to take steps to capturea checkout token associated with the point of sale. Processing at 430may also include presenting a list of payment options to the customer.For example, the mobile device may display all of the customer's paymentaccounts that have been registered with the system. This allows acustomer to view their available accounts (and, in some embodiments, thebalance available on each account as well as other information) prior tocompleting a transaction.

For example, in some embodiments, the customer may be prompted to pointa camera of the mobile device 202 at a bar code image of a checkouttoken and operate the mobile device 202 to capture the image. As anotherexample, the customer may be prompted to key enter the checkout token orotherwise enter it into the mobile device 202. In some embodiments, thecheckout token 210 is captured by a camera or other image capture deviceof the mobile device 202 (e.g., as shown in the screen shot of FIG. 8A).For example, in some embodiments, the mobile application (downloaded andinstalled at 310 in FIG. 3) is configured to automatically detect andcapture the checkout token 210 using a camera associated with the mobiledevice 202, or a wireless receiver.

In some embodiments, the camera may be operated in a continuous scanningmode where (without input from the user except, for example, a singlepush of the “Pay” button) the camera will rapidly (multiple times eachsecond) capture an image of the checkout token, each of which isprocessed by the mobile application until it successfully decodes theimage of the checkout token. This continuous scanning mode is useful,since it frees the user from repeatedly having to push the camera buttonto capture images in the case where the first images captured cannot bedecoded by the application, due to, for example, the image not beingclear enough due to the camera's viewfinder not completely capturing theimage of the checkout token or for other reasons. To optimize and speedthis process, the application may take into account specific attributesof the phone and its camera hardware, including the resolution of theimage captured, the focal length of the camera, and other attributes. Tofurther optimize the capture process, the size of the token, the angleof the surface on which the token is displayed, and other informationmay also be used to optimize the speed and accuracy of the checkouttoken capture process.

The mobile payment application installed on the mobile device 202 mayinteract with one or more other sensors (such as those described belowin conjunction with FIG. 7, including, for example, a magnetometer, agyroscope, and/or an accelerometer) during a capture process. In someembodiments, the payment application may interact with such sensors toimprove capture accuracy. For example, the mobile application may adjustcharacteristics or control of the mobile device's camera hardware (e.g.,such as by adjusting or controlling the image resolution and/or focallength of the camera), or adjust the algorithms and processes used tosearch the image data for a checkout token, based on data received fromsensors such as a magnetometer, gyroscope, accelerometer or the like.For example, data associated with a mobile device, it's sensors, andhardware characteristics (such as the focal length of the device'scamera, the model of the phone, etc.) may be used as inputs forcalculating a camera matrix or a projection matrix which is used toassist in compensating for image distortions including skew or the like.In this manner, data from mobile device 202 positioning or othercharacteristics may be taken into account when attempting to capturecheckout tokens, thereby ensuring accurate and consistent capture ofdata. Further, this data and these compensation techniques may be usedto more quickly locate a checkout token during an imaging or captureprocess.

As an illustrative example, referring to an example camera on an iPhonedevice, the projection matrix may be dependent on a few physicalcharacteristics, including the camera focal length (which is 3.85 mm forone version of the phone), the imaging plane (which is ½″ for the sameversion of the phone), the physical size of the position marks in acapture, and the physical distance between the position marks. Based onthis information, embodiments are able to identify a spatial locationfor position marks relative to the camera, and from that data, a tilt ofthe checkout token relative to the camera sensor may be calculated.Pursuant to some embodiments, a projection matrix (or camera matrix) isused to describe the tilt with respect to the camera sensor and is usedto adjust the capture process to ensure that checkout tokens may beefficiently and accurately captured even in situations where thecustomer is not holding the mobile device 202 in a manner where thecamera sensor is directly orthogonal to the capture token. By improvingthe capture process using these techniques, the customer experience andspeed and accuracy of capturing checkout tokens is improved.

In embodiments where the checkout token 210 is displayed in the form ofan encoded bar code image, the payment application installed on themobile device 202 may automatically operate to decode the bar code imageto obtain the checkout token 210. The encoded bar code image may bepresented in a number of different formats, including as a onedimensional or two dimensional bar code image or the like. In someembodiments, the checkout token 210 may be displayed as an unencodedstring of characters that may be key-entered into the paymentapplication of the mobile device. In some embodiments, the checkouttoken 210 may be read or entered into the payment application of themobile device using other means, such as, for example, by wirelesscommunication (e.g., such as by Bluetooth communication, by RFIDdetection, by optical character recognition, or the like). In someembodiments, processing may continue at 432 where the mobile device 202transmits the customer checkout token to the transaction managementsystem 230 as a customer transaction lookup request for payment accountinformation and transaction details. In some embodiments, thetransaction lookup request includes information associated with theidentity of the customer (determined during the authentication process).This information, coupled with information about the mobile device 202,allows the transaction management system 230 to determine that it isinteracting with an authorized user, allowing the system to locate theappropriate list of payment accounts for the user. As will be describedfurther below in conjunction with FIG. 4C, the transaction managementsystem 230 uses the checkout token and additional information receivedfrom the mobile device 202 to retrieve the transaction details receivedfrom the merchant (transmitted from the merchant at step 408 of FIG.4A), and to retrieve a list of the customer's payment accounts that aresuitable for the transaction.

Processing continues at 434 where the mobile device 202 receives thetransaction details and payment account information from the transactionmanagement system 230. For example, at 434, the device may receive amessage including a number of data elements, including data associatedwith the current transaction (such as the transaction total, themerchant name and information, and other transaction details) as well asdata identifying the customer's payment account(s) that may be used forthe current transaction, and information about the order in which thepayment accounts should be presented to the customer, as well asmarketing messages or advertisements that might be displayed inproximity to the payment account information. The data identifying thecustomer's payment account(s) may include proxies or non-sensitiveidentifiers used by the transaction management system 230 to identifyeach account (rather than the actual payment credentials). Further, thedata may include information about current account balances, loyaltyprograms, discounts, marketing messages, or the like associated with oneor more of the available payment accounts.

Processing continues at 436 where the mobile device 202, under controlof the mobile application, presents the transaction details and enhancedpayment account choice(s) to the customer on a display screen of themobile device 202. For example, if the customer (during the registrationprocess 300) provided information about one or more payment accounts,the customer may be given the opportunity to select which one(s) ofthose accounts are to be used in the current transaction. For example,the customer may be presented with a display of options such as the oneshown as FIG. 8B. In some embodiments, the display of options mayinclude information about the status of each of the available accounts(e.g., such as the balance, the current interest rate, any currentrewards or loyalty points, etc.) so that the customer may select themost appropriate account for use in the current transaction. In someembodiments, the actual payment account information is not stored in themobile device; instead, a non-confidential or non-sensitive identifieris used to identify the account (where the actual account number isstored at the remote transaction management system 230). In someembodiments, the customer may select to split the transaction among twoor more payment accounts.

Pursuant to some embodiments, the payment accounts available for use inthe payment transaction are displayed in a priority or preference orderbased on any combination of: (i) rules or preferences established by thecustomer (e.g., such as the rules or preferences defined by the customerat 308 of FIG. 3 during a registration process), (ii) rules orpreferences established by the merchant, (iii) rules or preferencesestablished by the issuer of a payment account, and (iv) rules orpreferences established by the transaction management system operator. Ahierarchy or ordering of rules or preferences and their priorities maybe specified to ensure that there are no conflicts between rules orpreferences.

In some embodiments, the payment accounts available for use in thetransaction are displayed in order based on one or more rulesestablished by the merchant or based on the identity of the merchant208. For example, the transaction management system may determine theidentity of the merchant based on the checkout token 210 and may thendetermine if any merchant-specific rules have been established. Examplesof merchant specific rules may include rules regarding interchange(e.g., such as rules which allow the merchant to reduce interchange byrequiring PIN entry for debit cards, etc), or presenting paymentaccounts in a top to bottom order where the top account is the one thatwhen used by the customer results in the merchant paying the smallestinterchange fee, and the bottom account is the one that when used by thecustomer results in the merchant paying the highest interchange fee.Merchant specific rules may also include rules specifying thatmerchant-controlled payment types (such as private label credit cards,gift cards, etc) are to be displayed with a higher preference than otheravailable payment types.

In some embodiments, the display of available payment accounts may alsoinvolve the application of one or more rules established by an operatorof the transaction management system 230. For example, in someembodiments, the transaction management system operator may becompensated (e.g., by issuers or sponsors) to display certain paymentaccount types with a higher priority. Those skilled in the art, uponreading this disclosure, will recognize that other types andcombinations of rules and preferences may be applied to display a listof available payment accounts to a customer during transactions of thepresent invention.

Processing continues at 438 where the customer interacts with the mobiledevice 202 (e.g., via a touch screen display or the like) to select adesired payment account (or payment accounts in the case of a splittender transaction) to use for the current transaction. In someembodiments, the customer may be presented with a confirmation screen at438 where the customer is prompted to confirm the transaction details(including the merchant, the transaction amount and the selected paymentaccount(s)). An example of such a confirmation screen and transactiondetails is shown at FIG. 8C. Once one or more payment accounts have beenselected for use, processing continues at 440 where a customer paymentauthorization request message is transmitted to the transactionmanagement system 230 for processing. In some embodiments, the messageincludes data such as information identifying the selected paymentaccount(s) as well as the transaction amount. In cases such as finedining (or transactions of the sort involving the addition of a tip orfurther amount after an initial transaction total has been generated),the present invention may allow the customer to change the transactionamount to include a tip amount for service, requiring that thetransaction amount be updated by the customer. The transactionmanagement system 230 receives the message and processes it as describedbelow in conjunction with FIG. 4C. If the transaction is successful(e.g., the transaction management system 230 is able to use the selectedpayment accounts to obtain a payment authorization from the financialinstitutions associated with the accounts), processing continues at 442where the mobile device 202 receives a transaction complete message.Examples of such a message are shown below in FIGS. 8D and 8E.

Reference is now made to FIG. 4C, where a further transaction process450 is shown. The process 450 generally shows steps from the perspectiveof the processing performed by the transaction management system (e.g.,the transaction process 450 includes a number of steps that may beperformed by a transaction management system, such as the system 230 ofFIG. 2, or by systems or components related to a transaction managementsystem to complete transactions pursuant to the present invention). Asdescribed above, the process 450 may be performed in conjunction withthe process 400 performed by the merchant 208 and process 420 performedby a mobile device 202. Processing begins at 452 where the transactionmanagement system 230 receives a merchant payment authorization request,including transaction data (such as a time stamp, terminal identifier,purchase details, or the like), an optional amount due (the “transactionamount”). The merchant payment authorization request may also include acheckout token or information used to assign a checkout token to thetransaction. The merchant payment authorization request may alsooptionally include a checkout token if the merchant has previously beenallocated a set of valid checkout tokens and is assigning those checkouttokens to transactions using its own system, rather than requesting themon a per transaction basis from the transaction management system. Themerchant payment authorization request is received from a merchant 208based on a transaction conducted by a customer who has selected to use amobile payment option pursuant to the present invention.

In some embodiments, the transaction management system 230 receives themerchant payment authorization request message (at 452) first, and laterreceives a customer payment authorization request message (at 470).However, in some embodiments, a two step process may be performed inwhich a merchant first transmits a merchant payment authorizationrequest (even prior to totaling a transaction for a customer) and thendoing an “update” to the merchant payment authorization request messagewhen the total has been calculated. In such embodiments, a customer maybe allowed to capture the checkout token at the beginning of thecheckout process so the merchant (or the transaction management system230) can present the customer with one or more targeted offers forviewing while the customer is in line or otherwise waiting for thetransaction to be totaled. The customer may, in such embodiments, bepresented with a message informing them that the system is “waiting fora total” on their mobile device along with the targeted offers. Once thetotal is calculated, the merchant systems send an update to the merchantpayment authorization request to the transaction management system whichincludes the total transaction amount, and then the customers' mobiledisplay would be updated to show the transaction details and the list ofpayment accounts with all rules applied.

Processing continues at 454 where the system 230 inserts the merchantpayment authorization request data into a merchant transaction queue. Insome embodiments, the merchant transaction queue is a queue thatcontains a set of “pending” or unmatched transactions that have beeninitiated at merchant locations. In some embodiments, merchant paymentauthorization request data stays in the queue until matched with acustomer payment authorization request received from a customeroperating a mobile device. In some embodiments, a merchant paymentauthorization request may “time out” or expire if a matching customerpayment authorization request is not received within a certaintimeframe. In other embodiments, the merchant payment authorizationrequests in the merchant transaction queue may not be sent to thetransaction management system; instead, they may reside on a server atthe merchant location or some other location, and the transactionmanagement system may have access to these merchant paymentauthorization requests so that it can match customer paymentauthorization requests received from mobile devices with the merchantpayment authorization requests residing on the server at the merchant'slocation.

Processing continues at 456 where a customer authentication request isreceived from a customer operating a mobile device 202 (e.g., thecustomer authentication request may be received as a result ofprocessing at step 424 of FIG. 4B). The customer authentication requestincludes customer authentication data as well as, in some embodiments,device authentication data. The transaction management system 230 usesthe received information to determine if the customer (and/or device)can be successfully authenticated based on information previously storedat or accessible to the transaction management system 230. For example,in the situation where a password authentication is required, processingat 458 may include a determination of whether the password received at456 matches a stored password for the customer. If the customer (and/ordevice) can be successfully authenticated, processing continues at 462,otherwise, processing continues at 460 where an authentication denial istransmitted to the mobile device 202.

If processing continues at 462, the system 230 operates to transmit anauthentication response to the mobile device 202 allowing the mobilepayment transaction to proceed. Processing continues at 464 where thesystem 230 receives a customer transaction lookup request message fromthe mobile device 202, including the checkout token (customer checkouttoken) from the mobile device. In some currently preferred embodiments,the message at 464 may also include (or be) a request for transactiondetails. Processing continues at 466 where the system 230 matches thecustomer checkout token received at 464 with a merchant checkout tokenreceived or looked up at 452. If a match is found, the transactiondetails associated with the merchant checkout token and thecorresponding merchant payment authorization request are used to createa response to the request at 468. Further, processing at 466 includesidentifying any payment account(s) associated with the customer that areavailable for use in the current transaction.

The transaction information (including merchant name and location andthe transaction amount, for example) and the available payment accountinformation, are transmitted to the customer's mobile device 202 at 468.Processing continues at 470 where the system 230 receives a customerpayment authorization request message which includes the customer'sselected payment account(s) for use in completing the transaction. At472, the system 230 uses the payment account information received at 470to lookup the actual payment credentials associated with the account(s)identified by the customer. The actual payment credentials may be storedin a system accessible to the transaction management system 230 which isPCI compliant (e.g., which securely stores and protects the actualpayment credentials). At 474, the actual payment credentials are used toobtain payment transaction authorization from the appropriate paymentnetwork and/or financial institution. The payment authorization responseis then sent to the merchant as well as to the customer at 476 tocomplete the transaction.

In this manner, embodiments allow payment processing to occur where thecustomer does not need to reveal payment account information to amerchant. Further, the customer is able to use a mobile device tocomplete the transaction. No card need be presented, nor does anycustomer information need to be transmitted over unsecured networks.Further, the customer can select from a number of different paymentaccount types and may even create split transactions (where differentaccount types are used in the same transaction).

To illustrate some embodiments of the transaction flow described above,an illustrative example will be provided (continuing the illustrativeexamples introduced above). Consider the example of the customer namedJane, who has an Apple iPhone and who has downloaded and installed thepayment application of the present invention and who has registered fourpayment accounts to be used with the system of the present invention. IfJane orders a coffee at a Starbucks and chooses to pay using the paymentsystem of the present invention, the clerk at Starbucks will ring upJane's coffee order on a merchant terminal and communicate the totalamount due to Jane. When Jane activates the payment application on herApple iPhone, she may be required to perform an authentication processto confirm her authority to use the payment application. Onceauthenticated, a list of available payment accounts may be transmittedto and displayed on a display screen of her iPhone.

A checkout token may be generated by the merchant systems at Starbucksand displayed on a point of sale display so Jane can then capture animage of the checkout token with her mobile phone. The paymentapplication on Jane's phone captures the checkout token, and transmits acustomer transaction lookup message to a remote system. The system usesthe token to match Jane's request with information sent from Starbucksabout the transaction, and also uses it to retrieve a subset of Jane'savailable payment accounts that are appropriate for use in making thisparticular purchase. The list of available payment accounts may beretrieved by the payment application on Jane's mobile devicecommunicating with the remote transaction management system (e.g., bycausing the transaction management system to look up the list of paymentaccounts Jane has registered, and to look up and apply any relevantrules or preferences). In this case, Jane has indicated a preferencethat her Starbucks gift card be used whenever possible. As a result, herStarbucks gift card will be displayed as the top payment choice for thistransaction. In some embodiments, an image of the card as well ascurrent balance information will also be displayed to Jane so that shewill know that she has sufficient funds to use the card.

Jane may then select to use her Starbucks gift card for the transactionby clicking on the image of the card and confirming her selection. Themobile device then transmits a payment request message to thetransaction management server indicating that Jane wants to use herStarbucks gift card to complete a purchase associated with a particularcheckout token for a particular amount. The transaction managementserver authorizes the transaction and sends a confirmation message toJane and to the Starbucks point of sale system. In this manner, Janeenjoys the ability to complete the transaction even if she forgot herpurse or her Starbucks card.

System Modules

Reference is now made to FIG. 5 where a block diagram illustrating asystem 500 pursuant to some embodiments is shown. The system 500 andmodules therein are provided for illustrative purposes only, andrepresent one possible implementation of a system pursuant to thepresent invention. Those skilled in the art will appreciate, uponreading this disclosure, that other implementations may also be used.System 500 includes a number of modules or components that, together,provide the functions of the transaction management system (such as thesystem 230 described above) to support the processing of paymenttransactions pursuant to some embodiments. System 500 may be deployed,for example, on one or more server systems. Those skilled in the artwill appreciate that this illustrative architecture is just one exampleof an implementation, and that a number of design and configurationalternatives may be provided to achieve the functionality of the presentinvention.

As shown, system 500 includes a transaction management system core 530interacting with a number of other components, including a mobilegateway 506 in communication with the transaction management system core530. The mobile gateway 506 may be a server or system configured tooperate as a mobile application communication enablement platform whichsupports multiple mobile devices such as iPhone and Android.Functionalities such as communication with transaction management systemcore 530 and customer management system 532 are implemented in thiscomponent. The mobile gateway 506 is used to handle communications andtransaction processing between the mobile payment application and thetransaction management system. The iPhone mobile application 508implements and optimizes screen flows, image capturing etc using aniPhone specific software development kit.

An ecommerce platform integration 522 may be provided which is acomponent that implements application programming interfaces whichenable the integration of the transaction management system with avariety of electronic commerce applications, including customapplications as well as commercial shopping cart applications. Theecommerce platform integration 522 may allow communication betweenelectronic commerce systems and the transaction management system core530 to allow payment transactions using features of the presentinvention to be implemented and performed in a variety of electroniccommerce systems.

A merchant POS integration system 520 may be provided that enablesvarious POS systems implemented in vendor specific technologies to beintegrated with the transaction management system. For example, theclient API may allow communication by and between PUS systems and POSterminals provided by NCR, IBM, Micros, Verifone, Ingenico or the liketo allow payment transactions pursuant to the present invention to beimplemented and performed using a variety of different POS systems andPOS terminals.

A customer management system 532 is provided to allow the management ofend customers using the payment system of the present invention. Thecustomer management system 532 allows the management, registration andadministration of customers, their profiles and provides functionalitiessuch as login to system and access to payment history and preferencedata.

A payment account management module 514 is provided to manage paymentaccounts of customers. The module 514 implements account creation,establishment of preferences, etc. The module 514, in some embodiments,maintains account information such as payment account details, paymentcard numbers, or the like. The module 514, in some embodiments, is PCIcompliant or otherwise configured to secure the payment accountinformation. In some embodiments, this module maintains sensitivedetails related to payment account data. The module 514 is closelyintegrated with the payment processing system 512 in such a way that thepayment processing system 512 need not store any sensitive account data.

A payment account third party service integration module 516 is providedto allow integration with partner systems to obtain information such asan account balance, or marketing messages for a payment account of acustomer as well as to obtain other payment account related information.

A merchant management system module 518 is provided to allow themanagement of retailer or merchant profiles, their identification codes,and the like. For example, the module 518 may manage the distribution,assignment and use of checkout tokens for each merchant location, sothat payment transaction requests received from customer mobile devicesmay be properly matched to pending transactions of the correct merchant.Other profile information, such as what payment instruments are acceptedby the merchant, or a list of current offers or promotions the merchantwants to present to users of the present invention, may also be managedby this system.

A transaction management system core 530 is provided to manage andmonitor all messages and transactions between the key components of theoverall system. The functionality supported by the module 530 isdescribed in general above in conjunction with FIGS. 1-4 and generallyprovides queuing and transaction matching and management fortransactions between mobile applications and POS systems, ecommerceshopping carts, and the system components presented in FIG. 5.

One or more gateway integration modules 504 are provided to serve as aninterface or bridge between the payment processing system module 512 andone or more payment gateways (such as those provided by ChasePaymentech®, Authorize.net, or the like).

A number of support and management modules may also be provided. Forexample, in some embodiments, a security management system module 524may be provided to manage and provide security functions for the system500, including the management of security keys, and roles andprivileges. In some embodiments, an auditing module 536 is provided toperform auditing activities as specified by administrators. A CSR systemmodule 534 is provided as a portal for customer service for merchants,end customers, and other entities. An admin portal module 528 isprovided to perform all administration functions such as configurations,updates, account maintenance, etc. for merchants, end customers, andother entities. A reporting module 526 is provided to provide access toinformation and data for administrators, merchants, and end customers.

Those skilled in the art will appreciate that a number of other modulesmay be used to provide service, management, administration and otherservices to the system 500.

System Modules—Transaction Flow Overview

Reference is now made to FIG. 6, where a block diagram of a system 600pursuant to some embodiments is shown illustrating one exampleembodiment of a transaction flow between selected modules or componentsof the payment system 600 pursuant to some embodiments of the presentinvention. The components of system 600 generally correspond to thecomponents shown and discussed above in conjunction with FIG. 5 (andalso include a number of external components such as those describedabove in conjunction with FIG. 2, such as point of sale devices, mobiledevices, and the like). Those skilled in the art, upon reading thisdisclosure, will appreciate that payment system 600 is an illustrativeembodiment, and that a number of variations of the illustrated systemarchitecture and flows may be made to deploy embodiments of the presentinvention.

The block diagram of FIG. 6 shows a number of illustrative messages thatmay be generated between components of an illustrative system accordingto some embodiments of the present invention. Each of the messages (or“steps”) that make up an example transaction are labeled with a numericidentifier on FIG. 6. A brief description of each of the “steps” areprovided below. Those skilled in the art will appreciate that this isbut one example of an implementation pursuant to the present invention.

At step “1”, a message is transmitted from a mobile application onmobile device 602 to the customer management system module 612. When acustomer wishes to conduct a payment transaction at a merchant, thecustomer interacts with the mobile application on the customer's mobiledevice 602 to initiate a login request with customer identificationinformation. The login request may include a userid and password,personal identification number or other authentication challenge toauthenticate the customer. Processing at this step may includeprocessing to authenticate the mobile device 602 by comparing storedinformation about the customer's registered mobile device to theinformation received from mobile device 602. For example, this hardwareor device authentication may include comparing stored details about thedevice to identifiable details transmitted in the message from themobile device 602 (such as hardware identifiers, serial numbers, or thelike, as discussed above).

Once the customer has been successfully authenticated, an Ads and Offersmanagement system 638 may be accessed to retrieve any advertisements oroffers that should be displayed to the customer in conjunction with thecustomer receiving a login response message indicating that they havebeen authenticated. The Ads and Offers management system 638 serves as agateway enabling the transaction management system 630 to accessadvertisements and offers available from a variety of sources, includingadvertising and offer management systems and networks such as thoseoperated by Google®, Microsoft®, Apple®, Yahoo®, Catalina Marketing®,and others. The transaction management system 630 may pass to the Adsand Offers management system non personally identifiable informationrelated to the customer, information about the merchant (including themerchant's location), and information about the items being purchased orthe payment instruments being considered in order to present to thecustomer the most relevant advertisements and offers at different timesduring the customer's use of the present invention. Ads and offers maybe presented to the customer at any time when they are using the mobiledevice 602, including immediately after they have been authenticated,when they are deciding which payment instrument to use to make apayment, and after the payment has been completed and they are presentedwith an electronic receipt or e-receipt on the mobile device 602.

At step “2”, the customer management system module 612, upon receipt ofthe login request from the customer, transmits a login request messageto the security management system module 624. The security managementsystem module 624 processes the login request by comparing receivedcredentials (and any authentication data) to stored data to authorize ordeny the login request. At step “3” the security management systemmodule 624 transmits a login response message to the customer managementsystem module 612. In this way, multiple modes of authentication areprovided to authenticate the customer as well as the device. A number ofvariations of validation processes may be followed. For example, in oneembodiment, an authentication may proceed as follows: (1) a customerlaunches the mobile payment application on their mobile device, (2)mobile device-related information is validated, and (3) the customercredentials are validated (e.g., by prompting the customer to provide ausername, password or PIN). Those skilled in the art will appreciatethat other authentication processes and flows may be used.

At step “4”, the customer management system module 612 transmits apayment account summary message to a payment account management systemmodule 614. The payment account management system would contain a listof all of the payment accounts the customer had registered with thesystem, including balance information and other details cached on thesystem. In most cases, the payment account management system wouldreturn the list of accounts and related information to the mobiledevice, as shown in step 8. In the case where the payment accountmanagement system needed to refresh the balance information associatedwith one or more payment accounts, the payment account management systemmodule 614 (at step “5”) would translate the payment account summarymessage request message into one or more requests that may be processedby the financial institution(s) that issued the accounts, or a financialinstitution intermediary with the ability to access the accounts. Theserequests would then be processed by a payment account—third partyservice integration module 616. The response (with account balanceinformation and details) is received via the message at step “6” andthen is passed back to the customer management system module 612 at step“7” for transmission to the mobile device 602 at step “8”. The messageat step “8” may also include a login response message along with anyother appended messaging from the customer management system module 612(such as any account updates or notifications that need to be presentedto the customer). At this point in time, the customer is logged in tothe payment application on his or her mobile device 602, and knows theaccount balance of any payment accounts that may be used in the presenttransaction.

In addition, at step “8”, the transaction management system 630 mayaccess the Ads and Offers management system 638 to locate appropriateads and offers to present to the customer (on a display screen of themobile device 602) in conjunction with the list of available paymentaccounts. Some of the offers or advertisements might appear on thevisual representation of a payment account on the display screen. Anexample of such a presentation of an offer is the “Additional 5% off ifused today!” offer shown on payment account 844 a in FIG. 8 b. In someembodiments, some messages, such as messages “1” and “8” may beprocessed through the mobile gateway.

In the situation where the customer is making a purchase using thepresent invention using an online shopping cart (e.g., such as in acheckout of an electronic commerce store), processing continues at thestep labeled “9” (in communication with the shopping cart 640). In thesituation where the customer is making a purchase using the presentinvention at a physical merchant point of sale (“POS”) location,processing continues at the step labeled “9” (in communication with thePOS device 609). In general, the messaging is similar in nature and willbe described together for simplicity. Processing at step “9” involvesthe generation and transmission of a message from the shopping cart 640or the POS 609 to the transaction management system 630 notifying thetransaction management system 630 of the customer's selection of thepresent invention as the customer's payment choice for a particulartransaction. The message at “9” includes information to notify thetransaction management system 630 about the initiation of a transactionat the merchant associated with the shopping cart 640 or the POS 609.The notification may include details of the purchase amount, time andother information, including a merchant identifier. The transactioninformation received at “9” will be placed in a pending transactionqueue at the transaction management system 630 awaiting subsequentinformation from the customer and mobile application to complete thetransaction.

The transaction process continues at step “10” where the transactionmanagement system 630 transmits a request to the merchant managementsystem module 618 to authenticate the merchant and obtain merchantinformation associated with the merchant at which the POS 609 orshopping cart 640 transaction is taking place. At step “11”, themerchant management system 618 transmits an authentication success orfailure message back to the transaction management system 630, alongwith merchant information if the authentication request is successful.The merchant information may include detailed information associatedwith the merchant (such as, for example, the merchant name, address,and, in some embodiments, a unique merchant identifier which may be usedto identify any relevant loyalty, rebate or other information that maybe matched to the present transaction).

At step “12” the transaction management system 630 transmits a checkouttoken to the shopping cart 640 or the POS 609. The checkout token may beeither generated for the transaction or retrieved from a set of one ormore available checkout tokens. Pursuant to some embodiments, themessaging at steps “9” through “12” are done in the same “session”without terminating the shopping cart or POS session.

At step “13” the mobile application installed on the mobile device 602is operated to transmit a message to the transaction management system630 to notify the transaction management system 630 of the customer'sintent to use the payment system of the present invention in thetransaction. The message at “13” may include a checkout token whichcould be a decoded bar code, or a code keyed in by the customer, or acode derived from a wireless signal along with customer and devicedetails. At message “14”, the transaction management system 630transmits a request to the security management system module 624 with arequest to perform any necessary security checks on the customer anddevice information provided from the mobile device 602.

At “15”, the security management system module 624 sends a responsemessage to the transaction management system 630 with information aboutthe security status of the mobile device 602 (and, for example, thestatus of the customer's account). Processing continues at “16” wherethe transaction management system 630 transmits a response to the mobileapplication on the mobile device 602 with information including themerchant information and the transaction details. The response “16” tothe mobile application may include advertisements and offers from theAds and Offers management system 638. At this point, the targeting ofthe ads and offers, in some embodiments, may be based on a rich set ofdata, including the customer's profile, the merchant's profile and thelocation of the store where the checkout event was occurring, the timeof day, the items being purchased, the payment instruments that areavailable to the customer, and a number of other factors. Thetransaction management system 630 may pass some or all of thisinformation to the Ads and Offers management system 638 which mayinteract with one or more ad and offer networks and select the offers topresent to the customer on the mobile device 602 that have the highestprobability of motivating the customer to act on one of the offers oradvertisements.

At this point in time, the mobile application and the customer have beenauthenticated, and the mobile application now has detailed informationabout the merchant and the pending transaction (including, for example,the total payment amount requested by the merchant).

The transaction process continues at “17” where the mobile applicationon the mobile device 602 sends a customer payment authorization requestmessage to the transaction management system 630. In particular, beforegenerating and transmitting message “17”, the customer selects whichpayment account he or she would like to use for the transaction. Thecustomer may select from a variety of available payment accountsdisplayed by the mobile application on a display screen of the mobiledevice 602. The message transmitted at “17” may include a code thatrepresents the particular payment account to be used by the customer(that is, the actual payment account information is not transmitted at“17”—instead, a proxy or representation of the payment account is sent).

At “18” transaction management system 630 creates a payment requestmessage using the information received at “17” and transmits the requestto payment processing system module 622. The payment processing systemmodule 622 (which is in a PCI compliant server system, for example)transmits a message “19” to a payment account management system module614 requesting a lookup of the actual payment account credentials forthe selected account. The actual payment account credentials stored atthe payment account management system 614 are then returned. The mappingbetween the proxy code and the real identifier (or actual paymentcredentials) is stored at the payment account management system 614. Theactual payment account number and other related payment accountinformation (such as, in the case of a credit or debit card, theexpiration date) is then sent to the payment processing system module622 at “20” to allow the module 622 to create a payment authorizationrequest message “21” for submission to a payment gateway module 636through a payment gateway connector 604 message “22”. A paymentauthorization or decline and other status and related information may bereturned from the gateway 636 to the payment processing system 622 viathe payment gateway connector 604 which receives the authorizationmessage via step “23” and passes the information back to the paymentprocessing system module 622 at “24” for return to the transactionmanagement system 630 at “25”.

If the transaction is authorized, the transaction confirmation message(the transaction authorization or decline message) is transmitted to theshopping cart 640 or POS 609 at “26” to complete the transaction. Atransaction completion (a transaction authorization or decline) messageis also sent to the mobile application of the mobile device 602 at “27”.

Those skilled in the art will recognize that other transaction messagesmay be provided, and other configurations of modules may be used tocomplete payment transactions pursuant to the present invention. Theconfiguration of FIG. 6 is provided to illustrate one example embodimentof the present invention.

Mobile Device

Reference is now made to FIG. 7, where a block diagram is showndepicting components of a mobile device 700 pursuant to someembodiments. As depicted, the mobile device 700 includes a number ofcomponents which may be controlled or perform functions in conjunctionwith one more application programs 710-712 to perform the features ofsome embodiments.

The mobile device 700 can include a memory interface 702 one or moredata processors, image processors and/or central processing units 704,and a peripherals interface 706. The memory interface 702, the one ormore processors 704 and/or the peripherals interface 706 can be separatecomponents or can be integrated in one or more integrated circuits. Thevarious components in the mobile device 700 can be coupled by one ormore communication buses or signal lines.

Sensors, devices and subsystems can be coupled to the peripheralsinterface 706 to facilitate multiple functionalities. For example, oneor more sensors, including a biometrics sensor 714, an accelerometer716, a photoelectric device 718, a proximity sensor 720, a camera 722, awireless communication unit 724, an audio unit 726 and a magnetometer728 may be provided to facilitate the collection, use and interactionwith data and information and to achieve the functions of the paymentapplications described herein. For example, when provided, themagnetometer 728 may be used to calculate a position of the mobiledevice 700 in space, allowing improved capturing of checkout tokens.

The mobile device 700 may include one or more input/output (I/O) devices730 and/or sensor devices. For example, input controllers 734 may beprovided with a speaker and a microphone (not shown) to facilitatevoice-enabled functionalities, such as phone and voice mail functions.In some implementations, a loud speaker can be included to facilitatehands-free voice functionalities, such as speaker phone functions. Anaudio jack can also be included for use of headphones and/or amicrophone.

The I/O subsystem 730 can include a touch screen controller 732 and/orother input controller(s) 734. The touch-screen controller 732 can becoupled to a touch screen 736. The touch screen 736 and touch screencontroller 732 can, for example, detect contact and movement or breakthereof using any of a plurality of touch sensitivity technologies,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith the touch screen 736.

The other input controller(s) 734 can be coupled to other input/controldevices 738, such as one or more buttons, rocker switches, thumb-wheel,infrared port, USB port, and/or a pointer device such as a stylus. Theone or more buttons (not shown) can include an up/down button for volumecontrol of the speaker and/or the microphone.

In some implementations, a proximity sensor 720 can be included tofacilitate the detection of the customer positioning the mobile device700 proximate to a point of sale terminal or display and, in response,to activate the camera or other reader to detect or capture an image ofa checkout token.

Other sensors can also be used. For example, in some implementations, aphotoelectric device 718 may be provided to facilitate adjusting thebrightness of the touch-screen display 738. In some implementations, anaccelerometer 716 can be utilized to detect movement of the mobiledevice 700, and a magnetometer can also be used to help detect theposition of the mobile device. In some embodiments, the mobile device700 may include circuitry and sensors for supporting a locationdetermining capability, such as that provided by the global positioningsystem (GPS) or other positioning system (e.g., systems using Wi-Fiaccess points, television signals, cellular grids, cellular towers, orUniform Resource Locators (URLs)). In some implementations, apositioning system (e.g., a GPS receiver) can be integrated into themobile device 700 or provided as a separate device that can be coupledto the mobile device 700 through a peripherals interface 706 to provideaccess to location-based services. The positioning and location-basedservices may be used, for example, to tag data transmitted from themobile device 700 to transaction management systems. For example, suchlocation data may be used to further identify the identity of a merchantwhich the customer is interacting with during a payment transaction, andmay also be used to assist in fraud detection by insuring that themobile device is in close proximity to the point of sale locationspecified in the information received in or derived from a merchantpayment authorization request.

The mobile device 700 can also include a camera lens and sensor 722. Insome implementations, the camera lens and sensor 722 can be located onthe back surface of the mobile device 700, or on the front surface. Thecamera can capture still images and/or video. The camera may be used,for example, to capture or capture images of a checkout token associatedwith a merchant point of sale location. In some embodiments, theoperation of the camera 722 may be controlled by a payment applicationinstalled on the mobile device 700. As a specific example, when thepayment application is activated to make a purchase transaction, thecamera 722 may be placed in a ready mode of operation so that as soon asthe camera lens and sensor 722 are placed proximate to a checkout token,the camera lens and sensor 722 may be operated to capture an image ofthe checkout token for use in the payment application.

The mobile device 700 can also include one or more wirelesscommunication subsystems 724, such as an 802.11b/g communication device,RFID, NFC, and/or a Bluetooth® communication device. Other communicationprotocols can also be supported, including other 802.x communicationprotocols (e.g., WiMax, Wi-Fi), code division multiple access (CDMA),global system for mobile communications (GSM), Enhanced Data GSMEnvironment (EDGE), 3G (e.g., EV-DO, UMTS, HSDPA,), 4G, LTE, etc.

In some implementations, additional sensors or subsystems may be coupledto the peripherals interface 706 via connectors such as, for example aUniversal Serial Bus (USB) port, or a docking port, or some other wiredport connection.

The memory interface 702 can be coupled to memory 708. The memory 708can include high-speed random access memory and/or non-volatile memory,such as one or more magnetic disk storage devices, one or more opticalstorage devices, and/or flash memory (e.g., NAND, NOR). The memory 708can store an operating system, such as Android, IOS from Apple, Darwin,RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system suchas VxWorks. The operating system may include instructions for handlingbasic system services and for performing hardware dependent tasks. Insome implementations, the operating system can be a kernel (e.g., UNIXkernel).

The memory 708 may also store application programs 710-712 which act, inconjunction with the processors 704, to cause the mobile device tooperate to perform certain functions, including the payment applicationrelated functions described herein.

The memory 708 can also store data, including but not limited todocuments, images (including payment account card images and imagescontaining advertisements and offers), video files, audio files, andother data. The mobile device 700 may be configured to operate using anumber of different operating systems and to communicate using a numberof different communications networks. Those skilled in the art willappreciate that the mobile device 700 may be sized as a handheld mobilephone, or other portable device such as a tablet computer or the like.

User Interface Examples

Reference is now made to FIG. 8A-8E which depict a number ofillustrative user interfaces that may be presented to a user operating amobile device (such as the mobile device 202 of FIG. 2) on a displayscreen of the device (such as the display 236 of FIG. 2) so that thecustomer can conduct payment transactions using features of embodimentsof the present invention. Each of the customer interfaces are shown asbeing displayed on an Apple iPhone mobile device—those skilled in theart will appreciate that similar user interfaces may be displayed onother mobile devices.

Referring first to FIG. 8A, a mobile device 802 is shown which has adisplay 836 showing an image of a checkout token (represented as adynamic two dimensional bar code image or “QR code” 837) which has beencaptured or imaged by a camera associated with the mobile device 802.The checkout token or code has been captured by a customer operating themobile device 802 during the course of a payment transaction usingembodiments of the present invention (e.g., the display shown in FIG. 8Amay have been captured during the transaction processing described atstep 430 of FIG. 4B, or step “13” of FIG. 6, etc.). In some embodiments,the mobile payment application running on the mobile device 802 isconfigured to automatically capture, decode, and transmit the codeduring the course of a transaction. While the code is shown as being anencoded two dimensional bar code image, those skilled in the art willappreciate that it may be displayed in any of a number of differentformats, such as, for example, a 1 dimensional barcode format such as aUPC, code 39, EAN 8 or EAN 13, other two dimensional formats such as PDF417 or Datamatrix, other n dimensional barcode formats, or alphanumerictext or symbols or the like.

The display of the mobile device 802 also includes a number of buttonsor icons 840, 842 which allow the customer to perform functionsassociated with the payment system of the present invention. Forexample, as depicted, the customer may choose to reset 840 the capturingof the checkout code (e.g., in the event that the code was not properlycaptured or read) or the customer may select among other choices 842including to clip or view special offers associated with the merchantlocation where the customer is currently shopping, view differentpayment accounts and related information, pay (which is shown as thecurrently selected option) or view more options.

Referring now to FIG. 8B, a further user interface is shown, again on adisplay device 836 of a mobile device 802. In the user interface of FIG.8B, the user has captured the checkout token or QR code (e.g., using thescreen of FIG. 8A), and has received a response message from atransaction management system (such as the system 230 of FIG. 2) withdetails of the payment transaction that the customer is about tocomplete. In particular, the transaction management system has returneddetailed transaction information about the purchase transaction,including merchant information and the purchase amount (shown as item842). The user interface also shows the customer a number of availablepayment options 844 a-n. The available payment options 844 a-n may beshown in the order of preference or desirability based on, for example,customer preferences or rules established by the customer (e.g.,pursuant to the process described above in conjunction with FIG. 3 orthe like), by the merchant, or by the payment system operator. Forexample, as shown, a private label credit card is displayed as the first(or top-most) payment account 844 a. Information about each of thepayment accounts 844 may be displayed, including the current availablebalance as well as any reward, loyalty or other benefits associated withusing that particular payment account in the current transaction.

In the user interface of FIG. 8B, the customer may select which of theavailable payment accounts 844 a-n to use by simply clicking on theportion of the screen associated with the available payment account 844a-n desired. In some embodiments, further information about eachavailable payment account may be viewed by clicking on a portion of thedisplay screen. For example, details of each accounts balance, terms andconditions and other information may be viewed. The user interface ofFIG. 8B may be presented to the customer in conjunction with transactionprocessing such as at step 436 of FIG. 4B, step “17” of FIG. 6.

Referring now to FIG. 8C, an (optional) further user interface is shownagain on a display device 836 of a mobile device 802. The user interfaceof FIG. 8C is an optional interface (in some embodiments, a user may godirectly from the interface of FIG. 8A or FIG. 8B to obtaining anauthorization, such as in the case where the user has specified a single“default” payment account to use for all transactions. In this case theuser may choose to not be presented with the interface of FIG. 8B, andwould instead go directly from the interface of FIG. 8A to obtaining anauthorization.). In the user interface of FIG. 8C, the customer hasselected which payment account to use and has been presented with ascreen to confirm the payment details using the selected paymentaccount. The user interface may display, for example, transactiondetails 846 and a confirmation button 848. The transaction details showthe detailed transaction information received by the mobile device 802from the transaction management system. For example, the user interfaceof FIG. 8C may be displayed after the customer has selected a desiredpayment account, and immediately prior to the transmission of a messageto the transaction management system (e.g., such as at step 438 of FIG.4B, step “17” of FIG. 6).

Referring now to FIG. 8D, a further user interface is shown, again on adisplay device 836 of a mobile device 802. In the user interface of FIG.8D, the customer has confirmed the purchase (e.g., by selecting“Confirm” 848 on FIG. 8C or by tapping on one of the payment accounts844 a-n in FIG. 8B, or by having specified a default payment instrumentto use for all transactions after capturing the checkout token as shownin FIG. 8A), and the payment message has been transmitted to thetransaction management system. The user interface of FIG. 8D shows thecustomer the details 850 of the just-completed transaction including anyloyalty rewards, rebate amount or the like earned from the transaction(shown at 854 as a savings amount). The user interface also shows aregion 856 where coupons, advertisements, or other offers sourced fromadvertising and offer management networks via the Ads and Offersmanagement system (such as the system 638 of FIG. 6) may be presented tothe customer. Once the customer is done viewing the transaction details,the customer may click on a button 852 to navigate away from the screenand to return to the home page of the payment application or to a thankyou page such as the page 858 shown in the user interface of FIG. 8E.

Those skilled in the art will appreciate that other user interfaces,messages and screens may be used to present payment options, transactioninformation and other details to a user of a mobile payment applicationpursuant to the present invention.

Although the present invention has been described in connection withspecific exemplary embodiments, it should be understood that variouschanges, substitutions, and alterations apparent to those skilled in theart can be made to the disclosed embodiments without departing from thespirit and scope of the invention as set forth in the appended claims.For example, transactions using the present invention may extend tosituations where a customer needs to add a tip or other service feeafter an original transaction total has been tallied, such as, forexample, when paying a bill at a restaurant, or when paying for a taxifare. In such situations, the amount due is optional, as the buyer maywish to add a tip after the transaction is initiated. In othersituations, such as taxi cabs, the taxi may just have displayed asticker with a barcode (where the barcode is a static checkout token),and capturing the sticker will link the buyer's payment account to thereceipt printer in the taxi once payment has been authorized.

In some embodiments, the system of the present invention can be used toinitiate and conduct “decoupled debit” types of transactions that: (i)do not require a physical plastic card with a magnetic stripe toinitiate a debit against a checking account at the point of sale, (ii)do not require a magnetic stripe reader to initiate a debit against achecking account at the point of sale, (iii) do not require the use ofthe standard point of sale transaction routing networks—VISA, MC,Discover, etc. to route transactions to the Federal Reserve's ACHnetwork. A number of advantages are provided, for example, (i) lowertransaction costs for merchants—by bypassing the card swipe terminal atthe POS and the associated payment transport networks—VISA/MC/Discover,etc. —embodiments are able to remove significant costs from the system,(ii) improved convenience for customers—the mobile form factor means thepayment instrument is always close at hand.

In some embodiments, merchants are provided with a new way to acceptchecking account payments at a physical point of sale without requiringthe customer to physically present a check to the merchant. Today, NACHArules specify how check payments may be originated at the point of sale,including specifying “origination codes” that specify the type of theACH transaction. Today, the only way that a merchant can take in anelectronic check from a customer at a physical in store point of sale isto either: (i) capture a scanned image of the check via a check21scanner, or (ii) follow a NACHA defined process to create an ACHtransaction with an origination code of POP, which stands for Point ofPurchase Check Conversion. Embodiments allow transactions to beconducted at the point of sale using the NACHA WEB transaction type.

In some embodiments, a POS to payment authorization device tokencapturing system is provided that is token delivery mechanism agnostic.For example, the mobile device works with both near field communicationor barcode or multi-dimensional barcode recognition techniques to link atransaction initiated at the POS with a corresponding authorizationmessage sent by the customer from their mobile device to authorize thetransaction. In some embodiments, systems of the present inventionprovide customer initiated delivery of both payment and loyaltycredentials to online and/or physical POS using a mobile device. Forexample, during processing of a transaction, both loyalty and paymentaccount information associated with the customer may be retrieved andpresented to the customer during a transaction (and, in someembodiments, the loyalty account may be automatically applied to alltransactions at a participating merchant) allowing ready and efficientinsertion of loyalty and payment information in a single transaction.

1. A method for operating a mobile device to complete a paymenttransaction between a customer and a merchant, where the merchanttransmits a merchant payment authorization request message to atransaction management system to initiate transaction processing, themethod comprising: causing a checkout token to be captured by the mobiledevice, the checkout token presented to the customer at a point of sale;transmitting, to said transaction management system, informationcaptured from said checkout token; receiving, from said transactionmanagement system, information associated with said payment transaction;and transmitting, to said transaction management system, a customerpayment authorization request message including information identifyinga selected payment account for use in completing said paymenttransaction.
 2. The method of claim 1, wherein said checkout token iscaptured prior to a calculation, by said merchant, of a total amount duein said payment transaction.
 3. The method of claim 2, wherein saidcheckout token is an identifier usable to lookup information associatedwith said merchant.
 4. The method of claim 3, wherein said checkouttoken further comprises information usable to identify at least one of(i) a timestamp, (ii) a merchant identifier, and (iii) a point of saleterminal identifier.
 5. The method of claim 4, wherein said informationassociated with said payment transaction received from said transactionmanagement system further comprises information identifying saidmerchant, the method further comprising: displaying said informationassociated with said payment transaction to said customer using adisplay screen of said mobile device.
 6. The method of claim 5, whereinsaid information associated with said payment transaction received fromsaid transaction management system further comprises informationidentifying a list of payment accounts associated with the customer, themethod further comprising: displaying said information associated withsaid payment transaction to said customer using a display screen of saidmobile device.
 7. The method of claim 5, wherein said informationassociated with said payment transaction received from said transactionmanagement system further comprises at least a first offer, said offerselected based at least in part on information from said merchantpayment authorization request message, the method further comprising:displaying said information associated with said payment transaction tosaid customer using a display screen of said mobile device.
 8. Themethod of claim 2, further comprising: receiving updated informationassociated with said payment transaction, said updated informationincluding said total amount due; and displaying said total amount due tosaid customer using a display screen of said mobile device.
 9. Themethod of claim 2, wherein said checkout token is a fixed tokenassociated with said merchant and said point of sale.
 10. The method ofclaim 2, wherein said checkout token is generated by said merchant foruse in said payment transaction.
 11. The method of claim 2, wherein saidcheckout token is generated by said transaction management system foruse in said payment transaction.
 12. The method of claim 1, wherein saidcheckout token is captured after a calculation, by said merchant, of atotal amount due in said payment transaction.
 13. The method of claim12, wherein said checkout token is an identifier usable to lookupinformation associated with said merchant.
 14. The method of claim 13,wherein said checkout token further comprises information usable toidentify at least one of (i) a timestamp, (ii) a merchant identifier,and (iii) a point of sale terminal identifier.
 15. The method of claim12, wherein said information associated with said payment transactionreceived from said transaction management system further comprisesinformation identifying said merchant, the method further comprising:displaying, on a display screen of said mobile device, informationidentifying said merchant and said total amount due.
 16. The method ofclaim 15, wherein said displaying information further comprises:displaying, on a display screen of said mobile device, a list ofavailable payment accounts and a request for selection of at least oneof said available payment accounts.
 17. The method of claim 15, whereinsaid displaying information further comprises: displaying, on a displayscreen of said mobile device, at least a first offer, said offerselected based at least in part on said information from said merchantpayment authorization request message.
 18. The method of claim 12,wherein said checkout token is a fixed token associated with saidmerchant and said point of sale.
 19. The method of claim 12, whereinsaid checkout token is generated by said merchant for use in saidpayment transaction.
 20. The method of claim 12, wherein said checkouttoken is generated by said transaction management system for use in saidpayment transaction.
 21. The method of claim 1, further comprising:transmitting, to said transaction management system, at least one of (i)customer and (ii) mobile device authentication data prior to saidtransmitting information captured from said checkout token.
 22. Themethod of claim 21, wherein the transmitting the authentication dataincludes establishing a connection between the mobile device and atransaction management system, wherein said transaction managementsystem is operable to compare said authentication data with stored dataabout at least one of the customer and the mobile device.
 23. The methodof claim 1, wherein said checkout token is presented using at least oneof: (i) an alphanumeric code, (ii) a code consisting of a combination ofletters, numbers or symbols, (iii) an encoded image including at leastone of (a) a barcode, (b) a QR code, and (c) an image pattern, and (iv)a wireless signal.
 24. The method of claim 1, further comprising:receiving, from said transaction management system, a list of availablepayment accounts for use in said payment transaction, wherein said listof available payment accounts is determined by at least one of (i) acustomer specified rule, (ii) a payee specified rule, and (iii) a systemspecified rule; and displaying, on a display device of said mobiledevice, said list of available payment accounts.
 25. The method of claim24, wherein said displaying said list of available payment accountsfurther comprises: displaying, on a display device of said mobiledevice, for each of said available payment accounts, at least one of (i)an available balance, (ii) an image representation of said paymentdevice, and (iii) offer information.
 26. The method of claim 24, whereindisplaying said list of available payment accounts further comprises:displaying, on a display device of said mobile device, in an order ofpreference for said payment transaction, wherein said order isdetermined by at least one of (i) a merchant rule, (ii) a user rule,(iii) a transaction management system rule, and (iv) a financialinstitution rule.
 27. The method of claim 1, further comprising:displaying, on a display device of said mobile device, a promotionalmessage, said promotional message based on at least one of (i) anidentity of the payee, (ii) a location of the payee, (iii) a time ofday, (iv) an identifier associated with one of the products beingpurchased as part of said payment transaction, (v) a shopping history ofthe customer, (vi) a shopping history of the customer, (vii) a profileof the customer, and (viii) the payment accounts used by the customer.28. The method of claim 1, wherein said information identifying aselected payment account is an identifier representing a payment accountassociated with a user of said mobile device, said identifier usable bysaid transaction management system to retrieve the actual paymentaccount details associated with said selected payment account.
 29. Themethod of claim 28, wherein said identifier representing a paymentaccount is an identifier assigned by said transaction management system.30. The method of claim 1, wherein said checkout token is printed usinga printer associated with said point of sale, wherein said checkouttoken is captured by at least one of: (i) capturing said checkout tokenusing a data capture device of said mobile device, and (ii) enteringsaid checkout token into said mobile device using a data entry device ofsaid mobile device.
 31. The method of claim 30, wherein said checkouttoken is printed as at least one of: (i) an alphanumeric code, (ii) acode consisting of a combination of letters, numbers or symbols, (iii)an encoded image including at least one of (a) a bar code, (b) a QRcode, and (c) an image pattern.
 32. The method of claim 1, wherein saidcheckout token is displayed on a display device associated with saidpoint of sale, wherein said checkout token captured by at least one of(i) capturing said checkout token using a data capture device of saidmobile device, and (ii) entering said checkout token into said mobiledevice using a data entry device of said mobile device.
 33. The methodof claim 32, wherein said checkout token is displayed as at least oneof: (i) a bar code image, (ii) an image pattern, and (iii) analphanumeric code.
 34. The method of claim 1, wherein said checkouttoken is captured from a terminal associated with said point of sale viawireless communication.
 35. The method of claim 1, wherein said checkouttoken is displayed proximate said point of sale, and wherein saidcheckout token is captured by at least one of: (i) capturing saidcheckout token using a data capture device of said mobile device, and(ii) entering said checkout token into said mobile device using a dataentry device of said mobile device.
 36. The method of claim 1, whereinsaid checkout token is captured by using at least one of: (i) an RFIDchip in said mobile device, (ii) a Bluetooth receiver in said mobiledevice, and (iii) a Wireless receiver in said mobile device.
 37. Themethod of claim 21, wherein said mobile device authentication dataincludes at least one of (i) a mobile phone number, (ii) a uniqueidentifier associated with an application installed on said mobiledevice, and (iii) a unique identifier associated with said mobiledevice.
 38. The method of claim 37, wherein said unique identifierassociated with said mobile device is at least one of (i) a hardwareidentifier, (ii) a serial number, (iii) a MAC address, (iv) an ASIN, and(v) a UUID.
 39. The method of claim 21, wherein said mobile device is asmart phone having a payment application installed in a memory thereof,wherein said transmitting customer authentication data furthercomprises: prompting said user for a passcode, said passcodeauthenticating said user to said payment application.
 40. The method ofclaim 21, wherein said transmitting customer authentication data furthercomprises: verifying an identity of said user based on at least one of:(i) a user identifier and password, (ii) a personal identificationnumber, (iii) a mobile telephone number, (iv) a facial recognition, and(v) a keyboard biometric process.
 41. The method of claim 21, whereinsaid mobile device is a Web-enabled phone, wherein said transmittingcustomer authentication data further comprises: pointing a browser ofsaid mobile device to a Web page associated with said transactionmanagement system; and prompting said user for a passcode, said passcodeauthenticating said user to said transaction management system.
 42. Amobile device, operable to conduct a payment transaction at a point ofsale device, the mobile device comprising: a display screen; acommunication port; a processor; a memory; and a program, wherein theprogram is stored in the memory and configured to be executed by theprocessor, the program including: instructions for causing a checkouttoken to be captured by the mobile device, the checkout token presentedto the customer at a point of sale; instructions for transmitting, tosaid transaction management system, information captured from saidcheckout token; instructions for receiving, from said transactionmanagement system, information associated with said payment transaction;and instructions for transmitting, to said transaction managementsystem, a customer payment authorization request message includinginformation identifying a selected payment account for use in completingsaid payment transaction.
 43. A method for operating a point of salesystem associated with a merchant to complete a payment transactionbetween the merchant and a customer operating a mobile device, where themobile device transmits at least one of customer and mobile deviceauthentication data to a transaction management system, the methodcomprising: transmitting, to the transaction management system, amerchant payment authorization request including information identifyingat least one of (i) the merchant and (ii) a point of sale device,presenting a checkout token to the customer for capture using the mobiledevice, the checkout token containing information associated with saidmerchant payment authorization request, the checkout token fortransmission from said mobile device to said transaction managementsystem; receiving, from said transaction management system, a paymentauthorization message; and completing said payment transaction.
 44. Themethod of claim 43, further comprising: after said presenting a checkouttoken to the customer for capture, calculating an amount due in saidpayment transaction; and transmitting, to the transaction managementsystem, an updated merchant payment authorization request includinginformation identifying an amount due in said payment transaction. 45.The method of claim 43, wherein said merchant payment authorizationrequest further includes information identifying an amount due in saidpayment transaction.
 46. The method of claim 43, wherein said checkouttoken is a fixed checkout token identifying said point of sale system.47. The method of claim 43, wherein said checkout token is a dynamiccheckout token containing information associated with said merchantpayment authorization request.
 48. The method of claim 43, wherein saidcheckout token is a dynamic checkout token containing informationassociated with said merchant payment authorization request, and whereinsaid checkout token is generated by said transaction management system.49. A point of sale system associated with a merchant, operable tocomplete a payment transaction between the merchant and a customeroperating a mobile device, where the mobile device transmits at leastone of customer and mobile device authentication data to a transactionmanagement system, the point of sale device comprising: a communicationport; a processor; a memory; and a program, wherein the program isstored in the memory and configured to be executed by the processor, theprogram including: instructions for transmitting, to the transactionmanagement system, a merchant payment authorization request includinginformation identifying at least one of (i) the merchant and (ii) apoint of sale device, instructions for presenting a checkout token tothe customer for capture using the mobile device, the checkout tokencontaining information associated with said merchant paymentauthorization request, the checkout token for transmission from saidmobile device to said transaction management system; instructions forreceiving, from said transaction management system, a paymentauthorization message; and instructions for completing said paymenttransaction.
 50. A method for operating a device to complete a paymenttransaction involving a customer and a merchant, the method comprising:receiving, from the merchant, a merchant payment authorization request,including information identifying at least one of (i) the merchant and(ii) a point of sale device; receiving a customer authentication requestfrom said mobile device and authenticating at least one of said customerand said mobile device; receiving, from said mobile device, a customertransaction lookup request including information captured from acheckout token; matching said information captured from said checkouttoken to information associated with said merchant payment authorizationrequest; identifying a set of available customer payment accounts foruse in said payment transaction; transmitting, to said mobile device,information associated with said merchant payment authorization requestand information identifying said set of available customer paymentaccounts; receiving, from said mobile device, a customer paymentauthorization request including information identifying at least onepayment account selected from said set of available customer paymentaccounts; and obtaining an authorization of said payment transactionbased on said customer payment authorization request.
 51. The method ofclaim 50, wherein said obtaining an authorization further comprise:retrieving actual payment account credentials based on said informationidentifying at least one payment account; and obtaining a paymentauthorization from a payment network using said actual payment accountcredentials.
 52. The method of claim 50, the program further including:transmitting a first payment authorized message to said merchant; andtransmitting a second payment authorized message to said mobile device.53. A transaction management system for use in completing a paymenttransaction between a customer operating a mobile device and a merchant,the transaction management system comprising: a communication port; aprocessor; a memory; and a program, wherein the program is stored in thememory and configured to be executed by the processor, the programincluding: instructions for receiving, from the merchant, a merchantpayment authorization request, including information identifying atleast one of (i) the merchant and (ii) a point of sale device;instructions for receiving a customer authentication request from saidmobile device and authenticating at least one of said customer and saidmobile device; instructions for receiving, from said mobile device, acustomer transaction lookup request including information captured froma checkout token; instructions for matching said information capturedfrom said checkout token to information associated with said merchantpayment authorization request; instructions for identifying a set ofavailable customer payment accounts for use in said payment transaction;instructions for transmitting, to said mobile device, informationassociated with said merchant payment authorization request andinformation identifying said set of available customer payment accounts;instructions for receiving, from said mobile device, a customer paymentauthorization request including information identifying at least onepayment account selected from said set of available customer paymentaccounts; and instructions for obtaining an authorization of saidpayment transaction based on said customer payment authorizationrequest.
 54. A method for operating a mobile device to conduct a paymenttransaction at a point of sale, comprising: receiving, by said mobiledevice, a checkout token associated with said point of sale; selecting afirst payment account for use in said payment transaction; transmittinga mobile payment request message to a remote transaction managementsystem, said mobile payment request message including informationidentifying said first payment account and said checkout token, saidmobile payment request message usable by said remote transactionmanagement system to authorize said payment transaction.
 55. The methodof claim 54, wherein said first payment account is a customer bankaccount, the method further comprising: receiving a debit authorizationrequest from said remote transaction management system, said debitauthorization request specifying a debit amount and a debit date;receiving an authorization from a user of said mobile device; andtransmitting a debit authorization response to said remote transactionmanagement system.
 56. The method of claim 55, wherein saidauthorization from a user is at least one of: a user-entered password, avoice authorization, and a digital signature.
 57. The method of claim55, wherein said debit authorization request further comprises datainforming said user of the user's right to revoke said authorization.58. The method of claim 55, further comprising: receiving, by saidremote transaction management system, said debit authorization response;generating a debit instruction identifying said customer bank account todebit, a debit amount, and a merchant bank account to credit; andcausing said debit instruction to be transmitted to a clearing housenetwork for processing.
 59. The method of claim 1, wherein said merchantpayment authorization request message is transmitted to said transactionmanagement system over a first network and said customer paymentauthorization request message is transmitted to said transactionmanagement system over a second network.
 60. The method of claim 1,wherein said causing said checkout token to be captured furthercomprises: determining a type of said checkout token, said typesselected from (i) an image, (ii) a wireless signal, and (iii) analphanumeric identifier; and capturing said checkout token using atleast one of (i) optical scanning, (ii) wireless scanning, and (iii) keyentry based on said type.
 61. The method of claim 1, wherein saidcausing said checkout token to be captured further comprises: adjustingan image sensor of said mobile device to adjust at least one of an imageresolution and a focal length based on data received from at least afirst sensor associated with said mobile device, said at least firstsensor selected from at least one of a magnetometer, a gyroscope and anaccelerometer.
 62. The method of claim 1, wherein said causing saidcheckout token to be captured further comprises: adjusting an imageprocessing algorithm operated by said mobile device to improve theability to locate a checkout token in image data by utilizing dataassociated with at least one of (i) a focal length of the mobiledevice's camera, (ii) a model of the phone, (iii) a resolution of theimage data captured by the mobile device's camera, (iv) data from themobile device's gyroscope, (v) data from the mobile device'smagnetometer, and (vi) data from the mobile device's accelerometer. 63.The method of claim 1, wherein said causing said checkout token to becaptured further comprises: detecting a request to capture a checkouttoken; and operating said mobile device in a continuous scanning mode,said continuous scanning mode causing said mobile device toautomatically capture multiple images in succession until said checkouttoken is detected.